Bhumika S, Anand Bagmar (Thoughtworks) How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback? We know what to test and how to test, but what is the right place to test it? In this workshop, we will demonstrate how we, as QA’s, can identify which tests can be classified as unit tests, integration tests, and functional tests. Using a case study, we will see how each component can be tested as part of unit testing; the integration of different parts and the functioning of a software system as a whole, and how functional tests fit into this big picture. We will then bring all these tests together to understand and build the testing pyramid and how it enables us to build the right testing framework with fewer Selenium, i.e., functional tests.

1. SAY “NO” TO MORE
SELENIUM TESTS
Anand Bagmar
Test Practice Lead
Bhumika Srinivas
Lead Quality Analyst

2. abagmar@gmail.com
Anand.Bagmar@thoughtworks.com
@BagmarAnand
about.me/anand.bagmar
ABOUT US
bhumikaiyengar@gmail.com
bhumika@thoughtworks.com
linkedin - bhumikaiyengar

3. What is
Test Automation?

4. Automation
-
A Safety Net

5. Why do we do
Test Automation?

6. QUICK FEEDBACK

7. Case Study

8. 8

9. 9

10. What does this
mean?

11. LEARNING
¨ Test each part thoroughly
¨ Unit
¨ Test ways of working together
¨ Component Integration
¨ Test how it all comes together
¨ Functional
This is how the parts becomes a Pen!
11

12. But …. what about the
things you do not see?

13. LEARNING CONTINUES …
¨ Test the Non Functionals
¨ NFRs
¨ Test the 3rd-party integration / interactions
¨ Integration
13

14. How does this
apply to Software?

15. 15

16. Flight
Search
Search
Results
Flight
Details
Passenger
Info
Payment Confirmation
Application Server
DB

17. LEARNING
¨ Test each part thoroughly
¨ Test ways of working together
¨ Test how it all comes together
¨ Test the Non Functionals
¨ Test the 3rd-party integration / interactions
¨ Understand Architecture – system & components
¨ Build Quality-in by Testing early
17

18. ACTION THE LEARNING
q Be inquisitive
q Ask a lot of Questions
q Why?
q How?
q When?
q What?
q Do Research
q Keep the “big-picture” in mind
18

19. How to get quick
feedback from
Test Automation?

20. TEST AUTOMATION PYRAMID
Unit
Manual / Exploratory
Integration
JavaScript
View
Web Service
UI
Cost
Impact
Time
Business-
facing
Tests
Technology-
facing
Tests

21. REALITY

22. ICE-CREAM CONE ANTI PATTERN
Manual / Exploratory
UI
Web Service
View
JavaScript
Integration
Unit

23. Web Service
View
JavaScript
Integration
Unit
Developers Test Pyramid QA Team Test Pyramid
DUAL TEST PYRAMID ANTI-PATTERN
Manual / Exploratory
UI
Web Service

24. CUP-CAKE ANTI-PATTERN

25. CONCLUSION
SAY NO TO MORE UI TESTS

26. abagmar@gmail.com
Anand.Bagmar@thoughtworks.com
@BagmarAnand
about.me/anand.bagmar
THANK YOU
bhumikaiyengar@gmail.com
bhumika@thoughtworks.com
linkedin - bhumikaiyengar