Agile tester 3.0
•Télécharger en tant que PPT, PDF•
4 j'aime•2,444 vues
How agile testers work? How many QAs profile can we have?
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Agile tester 3.0
Similaire à Agile tester 3.0 (20)
Plus de Daniel Amorim
Dernier
Dernier (20)
Agile tester 3.0
- 1. Daniel Ricardo de Amorim AGILE TESTER 3.0
- 2. About me! Daniel Ricardo de Amorim ● Agile QA Consultant at ThoughtWorks ● Speaker ● Writer ● amorim.danielricardo@gmail.com ● https://www.linkedin.com/in/danielricardodeamorim/en
- 4. How do agile testers work?
- 5. Terminologies ● Quality Assurance ● Quality Analyst ● Tester ● Test Engineer ● Software engineer in Test ● Lead QA ● Test Analyst
- 6. Testers are not sub-roles or separate roles in the team
- 7. Not a sub role anymore
- 8. Testers are part of the development team
- 9. Testers are engineers as well
- 10. What is the difference between an Agile Tester and a Developer?
- 12. But, are all QAs equal the same?
- 13. #not
- 14. What distinguishes QAs among themselves?
- 15. QA profiles can be sorted in three dimensions
- 16. Sort of QA's profile in 3 dimensions ● Business dimension ● Technical dimension ● DevOps dimension
- 18. Business driven
- 20. BDD is one of the techniques
- 25. Pair with devs
- 26. TDD and clean code enthusiasts
- 27. Experts on test automation
- 28. Knowledge on performance testing
- 29. Knowledge on security testing
- 32. DevOps dimension
- 36. All QAs
- 37. Keep the team focused on delivery
- 38. Concern about product's quality
- 40. Wear many hats
- 41. Infect the team
- 42. The bible
- 43. THANK YOU For questions or suggestions: Daniel Ricardo de Amorim damorim@thoughtworks.com
Notes de l'éditeur
- They are really business driven and client focus
- Extracting acceptance tests from clients is one of their specialities They're use to break down barriers between business context from the client side and technical context from the team.
- They use BDD to pair with devs and test the story since the beginning. They are also use to use ATDD, deriving goals from scope
- These QAs should have good programming skills to automate test and also help devs to build a good solution. As I already told you, there shouldn't be technical difference between QAs and Devs
- They will pair with devs to build the technical solution and they will code together. They will not just look at the code to give some guesses and tips about how to test. But they also will put their hands on the code and make this works.
- QAs will help devs to follow TDD practices to build a tested solution. They will ask devs about clean code, good practices and design patters to make good discussing on that and get the better conclusion to the solution
- They are experts on test automation, they need to help the team to create the better test strategy for each story played. They will help the team how to build the right test pyramid to keep the continous delivery practice on target all the time.
- They are experts on test automation, they need to help the team to create the better test strategy for each story played. They will help the team how to build the right test pyramid to keep the continous delivery practice on target all the time.
- They introduce the practice of continuous delivery and help the team create a continuous integration pipeline in order to get faster feedback after each commit.
- They automate repeatable tasks like run tests in their local machines, run code coverage and code quality tools.
- All QAs should keep their team focused on delivering business value to the client
- All QAs should keep their team focused on delivering business value to the client
- All QAs should keep their team focused on delivering business value to the client
- All QAs should keep their team focused on delivering business value to the client
- All QAs should keep their team focused on delivering business value to the client