TEST PYRAMID
Ramprasad
Manual / Exploratory
———
UI
———
Web Service
———
JavaScript
———
Integration
———
Unit
TEST AUTOMATION
Unit testing
Manual / Exploratory
UI
Web Service
View
JavaScript
Integration
Unit
Time
Value
Cost
Business-facing
Tests
Technology-facing
Tests
UI
Web Service
View
JavaScript
Integration
Unit
Manual / Exploratory
Developers Test Pyramid QA Team Test Pyramid
Web Service
View
JavaScript
Integration
Unit
Manual / Exploratory
UI
Web Service

Test Automation Pyramid

Editor's Notes

  • #5 Its essential point is that you should have many more low-level unit tests than high level end-to-end tests running through a GUI. Teams understand this. However, in many cases, fail to implement it the right way Alister Scott http://watirmelon.com/2012/01/31/introducing-the-software-testing-ice-cream-cone/
  • #7 Here is the structure of the talk: Explain why CI and CD are a necessity, and NOT a luxury. Discuss some of the factors that can make CD a reality. Discuss the current set of tools that assist in 'health-check' decision making for deploying / releasing the code in new environments. Explain the limitations of the above set of tools in the decision making process How can TTA bridge that gap (limitations discussed above)? Explain the value proposition for TTA Demo of TTA features Share the set of potential features to be added to TTA How can you help?
  • #9 Developers - Test Pyramid of Unit, System and Integration tests QA team - Test Pyramid of Functional Automation (UI and service layer) and Manual tests These pyramids are disjoint Lack of visibility into complete test coverage Duplication Holes