Super Marek's Testing Strategy (LeedsPHP meetup)

Talk presented at the LeedsPHP meetup.

Transcript

1. Super Marek’s Testing Strategy Photo from http://www.smartadvisoryltd.com/images/strategy.jpg
2. Marek Matulka @super_marek Photo by @cakper
4. no tests
6. my first unit tests
8. Price Quality Speed
9. Manual regression “testing” Some integration tests A handful of unit tests
10. Ealing Broadway Station
11. Problem Station building is small and overcrowded and at peak times people get stuck trying to change platforms. Station building connecting all platforms Platform 1 Platform 2/3 Platform 4 Platform 5/6
12. Solution Build a footbridge connecting rail platforms. Station building connecting all platforms Platform 1 Platform 2/3 Platform 4 Platform 5/6
13. Delivery Footpath connecting rail platforms. Station building connecting all platforms Platform 1 Platform 2/3 Platform 4 Platform 5/6 Footbridge
14. Result Still blocked platforms. Station building connecting all platforms Platform 1 Platform 2/3 Platform 4 Platform 5/6 Footbridge
15. Tester Detects bugs Prevents bugs QA
16. Who’s responsibility is testing?
17. QA
18. QA BE dev FE dev
19. QA BE dev FE dev PO UX BA
20. my team’s testing strategy
21. Definition of done • Have one • Change it as team’s delivery process changes • Have production environment from day one
22. Tools
23. Make tools work for you • Story board ◦ Virtual e.g. Trello, JIRA ◦ Physical e.g. stickies on the wall • Adjust as your process changes ◦ Visualise bottlenecks
24. Story grooming • Acceptance criteria • Testing strategy ◦ Unit tests enough? • Slice into smaller stories • Involve as many people as possible - QA, PO, FE, BE, stakeholders...
25. In development • Test early! ◦ Unit tests ◦ Acceptance tests ◦ Integration tests • Peer reviews • Pair programming • CI build on every commit
26. Quality Assurance • Run a build on each commit ◦ Make CI do the work for you • Static analysis ◦ Finds flaws missed in PR review • Env for every branch/PR ◦ Allows QA to verify work early, before it’s merged • QA to merge your PR
27. Monitoring • Logs collection ◦ logstash, papertrail • Bugs detection ◦ bugsnag, sentry • Alerts ◦ new relic, sysdig
28. Acceptance Criteria
29. Given-When-Then Feature: Shopper can see a postage cost In order to see the total cost of the order As a shopper I want to see a postage cost @APP-123 @smoke @database Scenario: Shopper can see a postage cost Given I have added a "Clean Code" book priced £34.50 to the basket And the postage cost for one book is £3.50 When I check the basket Then I should see the postage cost of £3.50 And the total of the basket should be £38.00
30. Write a failing scenario (feature) Write a failing test Make your test pass Refactor your code Make your scenario pass BDD TDD
31. Write a failing scenario (feature) Write a failing test Make your test pass Refactor your code Make your scenario pass BDD TDD External Quality Internal Quality
32. Unit tests Acceptance tests Integration tests E2E tests
33. Unit tests Acceptance tests Integration tests E2E tests $$$$$$ ¢ cost speed
34. Unit tests Acceptance tests Integration tests E2E tests Manual Automated
35. Price Quality Speed
36. Price Sustainability Speed
37. features delivered time
38. (on my current project) Example stack
39. Unit tests Acceptance tests Integration tests E2E tests
40. Thank you! https://speakerdeck.com/super_marek @super_marek