Erik Boelen - Testing, The Next Level
Download as PPT, PDF0 likes950 views
The document discusses the current state and challenges in software testing, emphasizing the need for testers to evolve and adapt. It highlights the importance of methodology flexibility, creative tool selection, and collaborative team dynamics for effective testing. Additionally, it advocates for the application of test-driven analysis to enhance the testing process.
Erik Boelen - Testing, The Next Level
- 1. Testing, the next level Challenges in software testing Erik Boelen QA Consult Services Erik.boelen@qaconsult.eu www.qaconsult.eu
- 2. Testing, the next level Erik Boelen2 What will I talk about? View on where we are in testing right now What are the challenges out there for us testers? Can these challenges help us grow as testers?
- 3. Testing, the next level Erik Boelen3 So where are we now? ‘In the starting blocks’ ‘Finally getting some structure in software testing’ ‘The future is looking bright for software testers!’ Opinion of peers My opinion? BOOTCAMP
- 4. Testing, the next level Erik Boelen4 So where are we now? Have you ever played computer games? Or any other games as such?
- 5. Testing, the next level Erik Boelen5 So where are we now? Remember the introduction screens? Or the moments where somebody explained the game during the first round? Guitar Hero Piper Panic Scrabble hints from your opponents?!
- 6. Testing, the next level Erik Boelen6 So where are we now? Computer games’ Boot camps In order to pick a weapon – E In order to fire a weapon – SPACE In order to holster – F In order to press a button – ENTER In order to activate a switch - A Enemy behind the door that is opened by a switch Now what?
- 7. Testing, the next level Erik Boelen7 So where are we now? Our instructions have been set – Methodologies – Testing principles – V-Model – ISTQB – IEEE Our instructions are ready to be challenged!
- 8. Testing, the next level Erik Boelen8 Challenges in software testing V-Model needs to be brought back to its roots Knowledge sharing needs improvement in software testing The objectives of testers within a project need to be fine tuned Look one step further in your tool selection Apply certain aspects of different methodologies in order to fit your need Think about test driven analysis … and many more
- 9. Testing, the next level Erik Boelen9 Apply the V-Model, do not use it According to TMap Next© Development Tests System Tests Acceptance Tests T We loose flexibility What is behind the label?
- 10. Testing, the next level Erik Boelen10 Apply the V-Model, do not use it Test Types Dev Test Test Types System Test Test Types Acceptance Test Test Stage 1 TS 2 TS3 Test Stage 4 T Test Basis Back to the roots
- 11. Testing, the next level Erik Boelen11 Apply the V-Model, do not use it Test Types are the drivers of testing – What to test? – How to test? – Where to test? – Who to test? Test basis is according to the V-Model principle! Test Levels are LABELS Test Stages give the flexibility to the project to – Define the test types; – According to their test basis; – Including the timing aspect V-Model applied and fit for purpose
- 12. Testing, the next level Erik Boelen12 Build, maintain and share knowledge Quick Google Research Type in a search string at Google and look at the first page results
- 13. Testing, the next level Erik Boelen13 Build, maintain and share knowledge Computer games – Walkthroughs – Guidelines – Tips & Tricks So many opportunities for testers – Blogs – Forums – Wiki – Online communities … and that’s just the internet Conferences – EuroSTAR Discussion groups
- 14. Testing, the next level Erik Boelen14 Set shared objectives Methodology says: ‘All testers need to be independent from the other skills within a project’
- 15. Testing, the next level Erik Boelen15 Set shared objectives All testers in a separate bubble? What about letting others in our bubble? – Designers – Developers – End users It’s the team effort that delivers projects Nothing new here! Specify team objectives in your entry & exit criteria of your testing process Release notes are written Test execution covers all requirements The end user approves the guidelines Team cooperation required!!
- 16. Testing, the next level Erik Boelen16 Be creative in your tool selection Easy to stay with the most common tools Make sure that you have the right tool for the job, not the most obvious one Practical example – If I need a tool to test usability, what can I do? Take an obvious tool and record test cases in there on usability, execute them and log the result – all textual Use the application Silverback and record all my actions, my visual expression and my voice while testing the new software – a lot more than just textual!!
- 17. Testing, the next level Erik Boelen17 Be creative in your tool selection
- 18. Testing, the next level Erik Boelen18 Combine testing methodologies ‘We use TMAP’ ‘We follow the SCRUM method’ ‘We only work iteratively’ ‘We combine methodologies in order to fit for purpose’ And very rarely
- 19. Testing, the next level Erik Boelen19 Combine testing methodologies Practical example We work in iterations while in a non-iterative environment, using exploratory testing as test preparation for scripted testing Clear combination of different approaches Fit for purpose!
- 20. Testing, the next level Erik Boelen20 Test Driven Analysis “Test-Driven Development (TDD) is a software development technique consisting of short iterations where new test cases covering the desired improvement or new functionality are written first, then the production code necessary to pass the tests is implemented, and finally the software is re-factored to accommodate changes. The availability of tests before actual development ensures rapid feedback after any change. Practitioners emphasize that test-driven development is a method of designing software, not merely a method of testing.” Used for more than a decade Most developers are OK with this According to Wikipedia
- 21. Testing, the next level Erik Boelen21 Test Driven Analysis Can we apply this to analysis? Are analysts OK to let testers in their bubble? ‘Test Driven Analysis (TDA) is a software analysis technique consisting of short iterations where new test cases covering the desired improvement or new functionality are written first, then the production of analysis documents to pass the tests are written, and finally, the analysis documents are re-factored to accommodate changes. ‘
- 22. Testing, the next level Erik Boelen22 Conclusion Get out of boot camp and face the challenges in testing Be creative Let people know about it Make sure you apply testing principles instead of just using them Do not get stuck at the instructions you get from others
- 23. Testing, the next level Erik Boelen23 Questions? Questions? Remarks? Challenges?