O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Agile tester 3.0

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
What is Agile Testing?
What is Agile Testing?
Carregando em…3
×

Confira estes a seguir

1 de 43 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Anúncio

Semelhante a Agile tester 3.0 (20)

Anúncio

Mais recentes (20)

Agile tester 3.0

  1. 1. Daniel Ricardo de Amorim AGILE TESTER 3.0
  2. 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
  3. 3. More http://www.thoughtworks.com/insights/blog/agile-tester-30
  4. 4. How do agile testers work?
  5. 5. Terminologies ● Quality Assurance ● Quality Analyst ● Tester ● Test Engineer ● Software engineer in Test ● Lead QA ● Test Analyst
  6. 6. Testers are not sub-roles or separate roles in the team
  7. 7. Not a sub role anymore
  8. 8. Testers are part of the development team
  9. 9. Testers are engineers as well
  10. 10. What is the difference between an Agile Tester and a Developer?
  11. 11. Are they enemies?
  12. 12. But, are all QAs equal the same?
  13. 13. #not
  14. 14. What distinguishes QAs among themselves?
  15. 15. QA profiles can be sorted in three dimensions
  16. 16. Sort of QA's profile in 3 dimensions ● Business dimension ● Technical dimension ● DevOps dimension
  17. 17. Business dimension
  18. 18. Business driven
  19. 19. Extracting acceptance tests
  20. 20. BDD is one of the techniques
  21. 21. Recommended books
  22. 22. Recommended books
  23. 23. Technical dimension
  24. 24. Programming skills
  25. 25. Pair with devs
  26. 26. TDD and clean code enthusiasts
  27. 27. Experts on test automation
  28. 28. Knowledge on performance testing
  29. 29. Knowledge on security testing
  30. 30. Recommended books
  31. 31. Recommended books
  32. 32. DevOps dimension
  33. 33. Continuous delivery
  34. 34. Automate repeatable tasks
  35. 35. Recommended books
  36. 36. All QAs
  37. 37. Keep the team focused on delivery
  38. 38. Concern about product's quality
  39. 39. Ownership of tests
  40. 40. Wear many hats
  41. 41. Infect the team
  42. 42. The bible
  43. 43. THANK YOU For questions or suggestions: Daniel Ricardo de Amorim damorim@thoughtworks.com

Notas do Editor

  • 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

×