Testing is probably the most misunderstood concept in software engineering. Many still believe that testing is simply a verification of actual and expected results in pre-defined set of test scenarios. I wish to know earlier how wrong this statement is. Conversations about testing can be seen wide, ambiguous, and hard to facilitate. But when done properly show prominent results. You start from quality. Addressing questions like. What does quality mean for us? Who owns it? Who is responsible for quality improvements? There is no single answer to every team. Each has to come up with their own definition, which works in their particular situation. Testing is not a measure for quality, but rather a set of activities and preparations to increase a level of confidence before releasing. You cannot simply state that after verifying 1000 test scenarios the whole product behaves as expected. During this presentation I will share key findings which I think are the most important ones to get almost any engineering team on the right track towards improving productivity and released product quality. There is no single rule to rule them all, but experience-based patterns.

1. Test coaching
your agile team

3. What is
test?

4. Test as a noun
(test cases, test scenarios, unit tests,
integration tests, system tests, functional
tests, end-2-end tests, ‘you name it’ tests)
artefacts, static document, static set of steps to be repeated

6. test automation
unconference

7. test automation certified

8. Quality
quality is everybody’s business
QAis not quality assurance but quality assistance
test automation is a responsibility of a person who
creates software

9. test automation pyramid

10. test automation tools and infrastructure

11. What else
test is?

12. Test as an activity (verb)
Testing using brain power
analysis, learning, exploration, experimentation
human side oftesting

13. test sessions

14. test(verb)
automation

15. Why coaching in testing?
tester’s role is somewhat undefined in ‘Agile’ teams
testing is often confused with checking therefore
very limited
testing done right brings value via preventing major
issue before end user sees it

16. How do you test
coach teams?
distinguish checking and testing
automate the routine
explore and learn what your product actually
does -> do this a lot!

17. thankyou.
andrii@spotify.com