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

Know Thy Product: Tips from a Tester

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 43 Anúncio

Know Thy Product: Tips from a Tester

Baixar para ler offline

Developers can't focus only on the details of their code – they have to look at the application from a user's perspective, too. Join Maria Heij from RefinedWiki AB for a journey into the tester's (and user's) mindset. She'll cover knowing how and why your product is used, understanding the intent behind requirements, and product implementations – all aimed at extending your skills and making your add-ons even better.

Maria Heij, Support & Test Manager, RefinedWiki

Developers can't focus only on the details of their code – they have to look at the application from a user's perspective, too. Join Maria Heij from RefinedWiki AB for a journey into the tester's (and user's) mindset. She'll cover knowing how and why your product is used, understanding the intent behind requirements, and product implementations – all aimed at extending your skills and making your add-ons even better.

Maria Heij, Support & Test Manager, RefinedWiki

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Quem viu também gostou (20)

Anúncio

Semelhante a Know Thy Product: Tips from a Tester (20)

Mais de Atlassian (20)

Anúncio

Mais recentes (20)

Know Thy Product: Tips from a Tester

  1. 1. Know Thy Product Tips from a tester MARIA HEIJ | SUPPORT & TEST MANAGER | REFINEDWIKI | @MARIAHEIJ
  2. 2. The USB office THINKING CRITICALLY
  3. 3. The user’s perspective I look at programs and applications from a user’s perspective.
  4. 4. The Holiday Candy Separated? Is the candy separated from each other? Taste? Do they taste like chocolate and mint? Chocolate? Is the candy covered in chocolate? Peppermint on top? Is there peppermint candy on top?
  5. 5. Put it into context Everything needs to be viewed in context of something. Find the intention There is a reason behind every requirement and feature. Why?
  6. 6. Agenda Your path through the product Users & data Report it Summing up
  7. 7. Agenda Your path through the product Report it Users & data Summing up
  8. 8. Agenda Your path through the product Users & data Report it Summing up
  9. 9. Agenda Your path through the product Users & data Report it Summing up
  10. 10. Your path through the product Users & data Report it Summing up
  11. 11. Do exploratory testing YOUR PATH THROUGH THE PRODUCT
  12. 12. Create a charter
  13. 13. First impressions, the test drive
  14. 14. The happy path Do exactly what you’re supposed to do. Think when and why.
  15. 15. The other paths Do it all! In a strange order! With strange tools! The happy path Do exactly what you’re supposed to do. Think when and why.
  16. 16. Writing documents and manuals
  17. 17. Why should this feature be used? How is this feature used? THE HOW THE WHY
  18. 18. PHRASE IT Figure it out, write it down
  19. 19. Explore the product, but plan your mission YOUR PATH IN THE PRODUCT
  20. 20. Screenshots Screen capture tool. Environment Records your environment. Log Test Sessions Logs time, issues and notes. Capture for JIRA
  21. 21. Your path through the product Report it Users & data Summing up
  22. 22. Step away from the admin login USERS
  23. 23. Know your audience
  24. 24. The Boss The admin. Can access anything. Will do anything. The Manager Assigns stuff. Creates content. Contributes. The Users Consume content. Have own agenda. Comment and like. The Watchers View content. Limited use. Like but don’t comment. Use personas
  25. 25. Step inside the shoes of your customers
  26. 26. Screen Sizes Change resolution, find different screen. Browsers Try them all. At least the ones you support. VPCs There are free options, use them! Mobile Devices Use an emulator and actual devices. Tools
  27. 27. Do you need to understand the data? Sometimes yes, sometimes no
  28. 28. Use real data, and reuse it DATA
  29. 29. Do support On a silver platter. Find a demo setup Sales team? Marketing? Demo? Sit in on meeting Customer meeting, consulting meeting, sales meeting. Watch someone else do it Find new ways. Don’t know where to start?
  30. 30. Your path through the product Users & data Report it Summing up
  31. 31. Who reads it? Is it clear and concise? How long does it live? The bug report
  32. 32. Who reads it? The bug report How long does it live? Is it clear and concise?
  33. 33. Who reads it? How long does it live? The bug report Is it clear and concise?
  34. 34. Writing the bug report REPORTING IT
  35. 35. What to do Steps to reproduce Expected result Actual result Metrics Project Prio Environment Example of bug report setup
  36. 36. Configure JIRA JIRA THE JIRAS
  37. 37. Your path through the product Users & data Report it Summing up
  38. 38. We’re in this together
  39. 39. Customer’s point-of-view Does it solve my situation? Is it consistent? Reasonable input of data? Developer’s point-of-view Reuse code? Optimize implementation? APIs?
  40. 40. The more you know, the better PUT IT INTO CONTEXT
  41. 41. Don’t just carry a rock, help build the pyramid
  42. 42. Thank you! MARIA HEIJ | SUPPORT & TEST MANAGER | REFINEDWIKI | @MARIAHEIJ

×