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? Using a case study, we will see how each component can be tested and 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. SAYING ‘NO’ TO
SELENIUM TESTS
Bhumika Srinivas
Senior Quality Analyst

2. ABOUT ME
2
Senior Quality Analyst @ MYOB
bhumikaiyengar@gmail.com
bhumika.srinivas@myob.com
linkedin - bhumikaiyengar

3. What is
Test Automation?

4. Automation
-
A Safety Net

5. Why do we do
Test Automation?

6. QUICK FEEDBACK
6

7. Case Study

8. 8

9. 9

10. What does this
mean?

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

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

13. LEARNING CONTINUES..
13
§ Test the Non Functionals
q NFR’s
§ Test the 3rd- party integration/interactions
q Integration

14. How does this apply to
Software?

15. 15

16. 16

17. LEARNING
17
§ 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

18. ACTION THE LEARNING
18
§ Be inquisitive
§ Ask a lot of questions – Why? How? When? What?
§ Do research
Keep the “big-picture” in mind

19. How to get quick feedback from
Test Automation?

20. TEST AUTOMATION PYRAMID
20

21. REALITY
21

22. ICE-CREAM CONE ANTI-PATTERN
22

23. DUAL TEST PYRAMID ANTI - PATTERN
23

24. CUP-CAKE ANTI - PATTERN
24

25. CONCLUSION
25
SAY NO TO MORE UI TESTS

26. THANK YOU
26
Senior Quality Analyst @ MYOB
bhumikaiyengar@gmail.com
bhumika.srinivas@myob.com
linkedin - bhumikaiyengar