The document debunks several common myths about testers and emphasizes the importance of their role in the software development lifecycle. It outlines three key principles for enhancing testing processes and promoting a positive culture in quality assurance, focusing on reducing lead time, fostering feedback, and encouraging learning. Overall, it highlights the need for collaboration and continuous improvement in testing practices.

1. Testing for Everyone
Mažvydas Skuodas @ Helis LT

2. Testers Myths
1. Testers get involved ONLY post development in the project life cycle
2. Testers will not become Project Managers
3. Reporting to Dev lead is a ‘block’ to a tester’s career
4. People with weak coding skills are assigned to testing
5. Testing is clicking at random places
6. Testing is just documentation/filling excel sheets
7. Testers have low pay scale
8. Testers do not get fame
9. Testers delay project delivery

3. Testers Myths
1. Everybody can do testing
2. Testing is boring
3. Testing is repetitive
4. Testers just moan about the code all the time
5. Testers slow down releases
6. Testers want everything to be perfect
7. Testers find stupid bugs that customers won’t ever find
8. Testers waste developers time

4. to Test - Take measures to check the quality,
performance, or reliability of (something),
especially before putting it into widespread
use or practice.

5. Tester Became QA
Quality Assurance

6. Programers loves tests

7. (most) Programers hates to write tests

8. 3 Ways

9. 1st Way
• The First Way enables fast left-to-right flow of work from Development to
Operations to the customer.
• In order to maximize flow, we need to:
• make work visible,
• reduce our batch sizes and intervals of work,
• build in quality by preventing defects from being passed to downstream
work centers
• and constantly optimize for the global goals.

10. 2nd Way
• The Second Way enables the fast and constant flow of feedback
from right to left at all stages of our value stream.
• It requires that we:
• amplify feedback to prevent problems from happening again
• or enable faster detection and recovery.

11. 3rd Way
• The Third Way enables the creation of a generative, high-trust
culture that supports a dynamic, disciplined, and scientific
approach to experimentation and risk-taking, facilitating the creation
of organizational learning, both from our successes and failures.

12. 1st: Reduce Lead time
2nd: Feedback
3rd: Learn and improve

13. http://itrevolution.com/the-three-ways-principles-underpinning-devops/

14. Tests provide instant feedback

15. The Experiment - A scientific procedure
undertaken to make a discovery,
test a hypothesis, or demonstrate a known fact.

16. http://itrevolution.com/the-three-ways-principles-underpinning-devops/

18. Games and Fun

19. What defines a game are the goal,
the rules, the feedback system, and
voluntary participation.

20. Gamers want to play the game. They want to
explore and learn and improve. They are
volunteering for unnecessary hard work - and they
genuinely care about the outcome of their effort

21. Exploratory testing

22. In high feedback games, the state of being
intensely engaged may ultimately be more
pleasurable then even the satisfaction of winning

23. Testing Tips

24. Step by step go up the hill..

25. QA Should find nothing

26. Reduce amount of testing
before we even begin

27. Don’t make programs look “buggy”
- show them how to improve them

28. Engagement - let them build
better stuff.

29. And Finally

30. Test is about Feedback,
and everybody needs feedback.

31. Any Feedback ?