The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.

1. Agile Testing Zbyszek Moćkun

3. Agile Testing

4. Process, Tester Principles

5. Agile against Waterfall (differences)

6. Continuous Integration

7. Builds, Test Automation

8. Managing issues found by Automated Tests, Test Case Management

9. Is it worth?

10. Pseudo Agile projects

11. Mini waterfall, No automation

12. Agile only during development phase

13. From Waterfall to Agile

14. Tester-Developer cooperation

16. QA and Testing QA measure quality of process Testing gives metrics

17. Agile Tester Principle Provide continuous feedback Deliver value to the customer Enable face-to-face communication Have courage Keep it simple Practise continuous improvement Respond to change Self-organize Focus on people Enjoy Lisa Crispin, Janet Gregory – Agile Testing

18. Agile Testing - Process InitialPlanning Release/New functionality

19. Agile against Waterfall Agile Waterfall Coding, newfunctionality Bug fixing Testing Release Iteration

20. Agile Testing - Iterations After each iteration we have finished stories and release is possible Waterfall – allnewfeatures (A,B,C,D,E,F) availableatthe same time, attheend of theproject

21. Continuous Integration Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Martin Fowler

22. Builds Continuous Integration How to integrate builds with Automation Tests When rebuild and run tests

23. Test Automation Tools (Selenium, Canoo Web Test, …) Technology (Html vs. Java,C,..) Who is reposnible for automation? Integration with Continuous Integration applications When start work on automation? Reporting

24. Manage Automation When run Automation tests Updating existing test scripts Automation test scripts for different releases, clients Creating new tests What automate, what not? Manage automation tests – Test Case Management Tools

25. Managing bugs How fast should we fix issues found by ATC? Should we raise official issues? Propagation issues for regression/UAT tests

26. Manual Tests How to manage manual and automation tests Still we need manual testing? When run manual tests When testing stories When testing bugs Managing issues

27. Test Case Management How do not mixed up with tests Why should we manage test cases How do not duplicate tests How report manual and automation tests Integration with automation tool and defect managment tools Test Case Managment tools

28. Agile vs. Waterfall Agile moves automation near development, which gives us less cost of fixing bugs Waterfall problem - often builds don’t pass smoke tests. Thanks moving automation, it almost not happen at all. QA in waterfall keep automaiton only for them Less manual testing in Agile

29. Is it worth? Agile Better for small projects Moves automation near development (better use) Better when good contact with customer Require experience and trainings New expirience Waterfall Big projects where requirement not change often Easier in managment Easier when team is located in different localizations

30. Pseudo Agile Projects Three examples of projects where Agile was introduce, but ... – from Tester perspective

31. Miniwaterfall Requirement Requirement Coding Coding & Fixing Coding Coding & Fixing Testing Testing Iteration 2 Iteration 1

32. Miniwaterfall Lack of automation tests Lack of Continuous Integration Complicated build system Lack of Resource

33. No automation It usually provides to miniwaterfall, which we describe previously. No releases after iteration, regression tests necessary Long time period between releases

34. Agile only during development phase Only developers work in Agile Just coding divided on iteratons No tests during development Automation (if exist) still stays on Test Team side Waterfall project Problems with builds from development

35. From Waterfall to Agile Few Tester Thoughts

36. Tester – Developer cooperation Agile One project team Close communication with developers (cooperate) The same aim Together analyze requirements, planning Parreralworkwithdevelopers Waterall Different team Mostly communication only by defect management tools Different aims Not involve in requirement analyzing, planning Time delaybetweencoding and tests

37. Tester concerns about Agile Tester manage by developer (project manager) Lost of identity No defined task (self-organize) No Agile training No carrier path Communication problem

38. Tester concerns about Agile Place in project Development skills only There is no Agile without automation There is no QA (Test) department on Agile project No exchange information between testers in different projects How I can develop my career

39. Q&A