"You should have many more low-level unit tests than high level end-to-end tests running through a GUI." - Mike Cohn

This statement has paved way for what is now popularly known as Test Pyramid.

Test Pyramid

[Picture Courtesy: http://martinfowler.com/]

Recent trends in Software development shows an increased focus on faster Time to market.
In most fast-paced environments, the divide between Developers and QAs are slowly diminishing.
Within teams following CD (continuous delivery), there is a need to re-think the way tests are written and the layers therein.

The term Application under test (AUT) no longer defines just the code written, but it also includes other integrations like Payment Gateways, Message Queue,  Worker processes and the Server instance itself. How can tests help in identifying problems in these areas? How will this affect the Test Pyramid?

The talk focuses on looking at various factors affecting faster time to market and discusses approach to solve the fore-mentioned.
Towards the end of the presentation, we will see the Test Pyramid adapted to faster delivery.


6 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

- Test Pyramid - A Quick look
- Continuous Delivery - What is it? Why are companies shifting towards (CD)
- Some patterns surrouding continuous delivery
- Role of QA
- Tests - What tests are required? and Why?
- Elaborating on the various tests taken up
- Conclusion - Re-drawing the lines in the test pyramid to give it a new look

Learning Outcome

The talk aims to change the way tests are layered.

Where to build the right safety nets is when implementing Continuous Delivery? - The talk will provide answers to this question.

Target Audience

QA Leads, Tech Leads, Architects

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Submission

  • Liked Simon Stewart

    Simon Stewart - Fix a Bug, Become a Committer

    Simon Stewart
    Simon Stewart
    WebDriver Creator
    schedule 2 years ago
    Sold Out!
    480 Mins

    Have you ever wondered how Selenium works under the covers? Do you get frustrated with locators not locating, pages not loading, or browsers behaving inconsistently from one run to the next? Selenium is an attempt to unify thousands of disparate elements across a wide spectrum of challenges into a single, common interface that works seamlessly with all the major browsers - and yet only a handful of volunteers work to maintain this gigantic effort. If you would like to enhance your own Selenium experience while contributing back to the software that has defined so many of our careers, come to this workshop. In it we'll dissect the different elements of Selenium, dive into its internals, learn how it was built and how to make changes to it, and even write a unit test you can contribute on the same day!

  • Liked Sargis Sargsyan

    Sargis Sargsyan - Better Page Object Handling with Loadable Component Pattern

    45 Mins

    One of the painful problems in Selenium automated testing is determining whether a HTML page has been loaded. This is especially the case when web application uses a JS  heavy framework such as the popular AngularJS.

    During this talk we will discuss how to handle Selenium Page Object pattern better with Loadable Component.

    The Loadable Component helps test case developers make sure that the page or a component of the page is loaded successfully. I will share my experience about the concept of the Loadable Component and Page Object patterns.