The modern ART of Automation Testing

Transcript

1. The Modern ART of Testing
2. You need two days to write test cases!? You already have the requirements specification. Just copy and paste from it. © Copyright 2016. 3Pillar | All rights reserved
3. Note that the build you are testing can change any time. Even if you notice that the build has changed, just continue your testing as if nothing has happened. © Copyright 2016. 3Pillar | All rights reserved
4. There is no need to test that module. I have already had a [senior] developer test it and he said it is working fine. © Copyright 2016. 3Pillar | All rights reserved
5. You have found a bug? Are you sure that you have tested the latest build [implying a very recent untested build]? © Copyright 2016. 3Pillar | All rights reserved
6. Finally, It is 8 p.m. The developers have worked very hard to create this release. Now, they have all gone home. You can do all your testing. Just remember that the release has to be delivered to the client first thing tomorrow morning. © Copyright 2016. 3Pillar | All rights reserved
7. What can we do? How can we improve? © Copyright 2016. 3Pillar | All rights reserved
8. We should... • Think outside the box • Make a plan always • Share thoughts before it’s too late • Explain the process • Be concise and clear with your thoughts • Find outstanding solutions • Resolve problems as puzzles • Find more than 1 solution to your problem • Present visual information • Ask as many questions as you can © Copyright 2016. 3Pillar | All rights reserved
9. Mastering situations.
10. That’s what they say: We... • don’t think this defect is worth fixing • can not replicate this defect • thought you already tested on IE • know testing won’t be finished until the release date • think you didn’t understand the requirements • agreed that automation testing will take too much • should stop testing • don’t have enough time © Copyright 2016. 3Pillar | All rights reserved
11. Mastering Automation Testing Success in test automation requires careful planning and design work. © Copyright 2016. 3Pillar | All rights reserved
12. Sometimes... • tests break for the wrong reasons and testers found additional bugs • automation tests steps take far longer than just executing them manually • the UI is one of the least stable interfaces of any system, so we can start automating quite late in the development phase • we’ll never able to finish full regression test On Time • maintenance of the automation tests takes a significant amount of time and we only have control of one small piece of PIE © Copyright 2016. 3Pillar | All rights reserved
13. Why? When? What? How? • Objective => analyze code + business • Test early => Implementation • To automate => establish some priorities ◦ Repetitive ◦ Cause human error ◦ Require multiple data sets ◦ High risk of defects ◦ Different hardware and software • Tools, Frameworks, Design Patterns => Ecosystem © Copyright 2016. 3Pillar | All rights reserved
14. Nevermind “fashion”, style is forever • Do more than just test • Automation + manual • Be creative • Don’t judge • Know the business • Take initiative • Be proactive • Don’t trust • Be a mythbuster! © Copyright 2016. 3Pillar | All rights reserved
15. Fake it till you make it! © Copyright 2016. 3Pillar | All rights reserved
16. ?
17. nagyalexandra28 alexandra.nagy@3pillarglobal.com