5. Bring questions
What’s wrong with our current small iterations?
Tuesday, November 22, 2011
6. Bring questions
What’s wrong with our current small iterations?
Trust developers to test the app??!!
Tuesday, November 22, 2011
7. Bring questions
What’s wrong with our current small iterations?
Trust developers to test the app??!!
What happens to our Selenium test suite?
Tuesday, November 22, 2011
8. Bring questions
What’s wrong with our current small iterations?
Trust developers to test the app??!!
What happens to our Selenium test suite?
We’ll be relegated to manual testers?
Tuesday, November 22, 2011
9. Bring questions
What’s wrong with our current small iterations?
Trust developers to test the app??!!
What happens to our Selenium test suite?
We’ll be relegated to manual testers?
How do we measure quality?
Tuesday, November 22, 2011
10. But first a little history...
Tuesday, November 22, 2011
11. But first a little history...
Tuesday, November 22, 2011
13. Simplified
What the team did before
Trunk/ Stage Prod
Dev
Tuesday, November 22, 2011
14. Simplified
What the team did before
Trunk/ Stage Prod
Dev
•Verify new features
•Is this the right thing?
•Automate
Tuesday, November 22, 2011
15. Simplified
What the team did before
Trunk/ Stage Prod
Dev
•Verify new features
•Is this the right thing?
•Automate
Tuesday, November 22, 2011
16. Simplified
What the team did before
Trunk/ Stage Prod
Dev
•Verify new features •IT pushes
•Is this the right thing? •Regression test
•Automate •Exploratory Testing
•Is this the right thing?
Tuesday, November 22, 2011
17. Simplified
What the team did before
Trunk/ Stage Prod
Dev
•Verify new features •IT pushes
•Is this the right thing? •Regression test
•Automate •Exploratory Testing
•Is this the right thing?
Tuesday, November 22, 2011
18. Simplified
What the team did before
Trunk/ Stage Prod
Dev
•Verify new features •IT pushes •IT pushes
•Is this the right thing? •Regression test •Verify
•Automate •Exploratory Testing •Wahoo!
•Is this the right thing?
Tuesday, November 22, 2011
19. The brave new world
Continuous deployment
http://cliptank.com/funny/dog-costumes.php
Tuesday, November 22, 2011
21. Discuss what is acceptable risk
https://wiki.mozilla.org/QA/Execution/Web_Testing/Continuous_Deployment#Risks_.26_Plans_.26_Tools
Tuesday, November 22, 2011
22. Discuss what is acceptable risk
Risk: Less critical areas will not be covered by
automation
https://wiki.mozilla.org/QA/Execution/Web_Testing/Continuous_Deployment#Risks_.26_Plans_.26_Tools
Tuesday, November 22, 2011
23. Discuss what is acceptable risk
Risk: Less critical areas will not be covered by
automation
•If the feature breaks, it is acceptable to wait up to
an hour for a fix.
https://wiki.mozilla.org/QA/Execution/Web_Testing/Continuous_Deployment#Risks_.26_Plans_.26_Tools
Tuesday, November 22, 2011
24. Discuss what is acceptable risk
Risk: Less critical areas will not be covered by
automation
•If the feature breaks, it is acceptable to wait up to
an hour for a fix.
• Example: the ability to answer a question.
https://wiki.mozilla.org/QA/Execution/Web_Testing/Continuous_Deployment#Risks_.26_Plans_.26_Tools
Tuesday, November 22, 2011
31. Manual strategy
Feature verification & exploratory testing
Testing can occur in production
Tuesday, November 22, 2011
32. Manual strategy
Feature verification & exploratory testing
Testing can occur in production
Community involvement on new features
Tuesday, November 22, 2011
33. Automation is fun
https://github.com/mozilla/sumo-tests
Tuesday, November 22, 2011
34. Automation is fun
https://github.com/mozilla/sumo-tests
Tuesday, November 22, 2011
36. Automation strategy
Selenium tests for areas that are clumsy to cover with unit
tests or QUnit
Tuesday, November 22, 2011
37. Automation strategy
Selenium tests for areas that are clumsy to cover with unit
tests or QUnit
Qualify as deployment blockers: run in dev & staging
envs
Tuesday, November 22, 2011
38. Automation strategy
Selenium tests for areas that are clumsy to cover with unit
tests or QUnit
Qualify as deployment blockers: run in dev & staging
envs
Non-volatile production tests verify env & services
work
Tuesday, November 22, 2011
39. Automation strategy
Selenium tests for areas that are clumsy to cover with unit
tests or QUnit
Qualify as deployment blockers: run in dev & staging
envs
Non-volatile production tests verify env & services
work
[All] Tests will be deleted if they don’t cover critical areas
Tuesday, November 22, 2011
40. Waffling
Failure is always an option
Tuesday, November 22, 2011
41. Waffling
Failure is always an option
Tuesday, November 22, 2011