O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Adventures in QA

1.371 visualizações

Publicada em

Adventures of a developer who suddenly found himself in the role of head of QA.

Presentation as held at ACCU 2010 (I think - had to recreate it from the last draft after I lost my laptop on the Eurostar in the ensuing volcanic chaos on the way back from Oxford).

Publicada em: Educação
  • I have done a couple of papers through ⇒⇒⇒WRITE-MY-PAPER.net ⇐⇐⇐ they have always been great! They are always in touch with you to let you know the status of paper and always meet the deadline!
       Responder 
    Tem certeza que deseja  Sim  Não
    Insira sua mensagem aqui
  • Seja a primeira pessoa a gostar disto

Adventures in QA

  1. 1. Adventures in QA Dirk Haun ACCU Conference 2010
  2. 2. Prelude
  3. 3. About me • For the longest time: Developer in C, C++ • Surprise career move to QA • Amateur in QA
  4. 4. Company Profile • Document conversion • Large scale • Highly portable C • Some Java
  5. 5. Important Features • Performance • Resources • Quality • Usability (in progress) • not so much: Security
  6. 6. Motivation
  7. 7. "Das ging doch schon mal?!"
  8. 8. "But this used to work?!"
  9. 9. My First Regression Test Suite
  10. 10. Career
  11. 11. Career Path
  12. 12. Corporate Siberia
  13. 13. The Job
  14. 14. "Make it work"
  15. 15. Develop Test Ship
  16. 16. Develop Test Ship improve here
  17. 17. Wiggle Room only
  18. 18. 3 Departments in 1
  19. 19. C vs. Java
  20. 20. Infrastructure
  21. 21. Old Hardware
  22. 22. Time to run tests
  23. 23. Storage
  24. 24. Intermission Some feedback from my helpful audience
  25. 25. Ideas from the Audience • Partioning - find the essential tests • Reduce release frequency for some of the platforms • Try differential pricing per platform
  26. 26. Ideas from the Audience • Don‘t just set up rules (guidelines, directives), but explain why • How do new people learn the rules? Try storytelling or mentoring • Test the rules
  27. 27. Ideas from the Audience • Get stakeholders involved, e.g. customers • Get an outsider‘s view, e.g. from a consultant
  28. 28. Changes
  29. 29. Quality as #3 problem
  30. 30. New Boss
  31. 31. Communication
  32. 32. New Rules
  33. 33. Theory vs. Practice
  34. 34. "Every new feature should have a test"
  35. 35. "This feature has to be in the next version"
  36. 36. Continuous Integration
  37. 37. Breaking the Build • acting on failed tests • figuring out who broke the build • time-consuming • whose responsibility is it? • running the unit tests before committing
  38. 38. Test Ownership
  39. 39. New tests • Providing test data • Adding the tests
  40. 40. Outlook
  41. 41. New Projects
  42. 42. Does everybody "get" it yet?
  43. 43. What about me?
  44. 44. (Some) Lessons Learned
  45. 45. Test Communities do exist
  46. 46. Change takes time - a lot of time
  47. 47. QA needs a "holistic" approach
  48. 48. Test automation - The Holy Grail?
  49. 49. The End?
  50. 50. Credits • Photos via flickr.com, thanks to: Hopkinsii, lotyloty, seier+seier, Alex Polezhaev, Horia Varlan, Caterina Fake, Steve Jurvetson, Stig Nygaard, Steve Punter, Peter Dutton, paul posadas, Erik Pitti, Nick J Webb, Bill Gantz, Jukka Zitting, Kevin Dooley, Jean-Pierre Dalbéra, Matti Mattila, Rebecca Krebs, mollybob, Matt Brown, Bob Bobster, James Bowe, Bhumika Guglani, manuki • Photos and names are links - click them!

×