The latest changes that came up to the software development industry influenced the daily work of everyones in the companies: developers, testers, business analysts, sales, hr etc.… The goal from business is to have shorter time to market. Talking about the quality of the system, we engineers are delivering, is crucial! How to test our application faster and effectively is more and more the topic of the discussions. Try to Google the answer and you will see two commons: implement Test Automation process and use Exploratory Testing . There are a lot of rumors around this. All that leads to misunderstanding what that practices are. I want to break the uncertainty around test automation, exploratory testing and would like to show you the real life examples that could help you. I won't show production code because of NDA but try to use demo project to show the principles behind

1. How To Manage Testing
in Dynamic
World
@adzynia
v 1.1.2

3. ?

4. Idea

7. Minimal Valuable
Product

10. GO
LIVE

11. AND ?
@adzynia

12. Fixing bugs
Missing features
Angry Users
Lack of time

13. Stress

14. QA

15. be Responsible for
Quality
Write test plan
write test cases
do manual testing
automate testing
To

16. To Do In Development Code Review Testing Demo
!
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
2 Days Before Demo
@adzynia

17. Outsource
testing?

18. Oh no...
How it can be different?

19. QA != TestingQuality is whole team responsibility

20. BA Dev Tester
User
Story

21. Look for consensus!
not compromise
WIN/WIN!WIN/lose
lose/WINlose/lose

22. 3 Amigo’s Meeting
Tester
Busines
s
Developer

23. Acceptance Scenarios
Testing Checklist
Testability Tasks
Outcome

24. Scenarios Demo
https://github.com/adzynia/cucumber-jvm-scrum-test

26. @adzynia

27. How to write
Acceptance Scenarios
Find more
at
adzynia.com

28. Manual Testing
Is
Still Important !
But

29. Checking != Testing
@michaelbolton

30. Session Based Test
Management
VS
Test Cases Management

31. Testing Session
should be:
Goal focused
Time-boxed
Reported
Debriefed

32. Learning
Design
Execution
Feedback
Exploratory testing
@jamesmarcusbach

33. ?
Regression
Testing

34. Functional Map

35. MOdel based
testing?
to be continued…

36. Release to
Production
should be
EASY

37. At the End you will get
Friendly Team
Living Documentation
Automated Acceptance Scenarios
Functional Map
Testing Session Reports
Stable Delivery Pipeline

38. To Do
Acceptance Test
Design
In Development Code Review Testing Demo
!
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
Development flow
User
Story
@adzynia

39. AND
Do not forget
about Balance
Control
Ad-hoc

40. @adzynia
adzynia.com
Email:
me@adzynia.com

41. To Read