Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Testing - presentation for Agile User Group


Published on

Agile testing was present on Agile User Group. Presentation covers all aspects of testing on agile process, highlight the role of automation and issues with managing it.

Published in: Business
  • 1) Of course, not always autoamtion is our aim. But I still think that only automation allow you to deliver high quality application in short time.

    7) Slide 7 - sorry, I missed requirement/story creation part. I do not wan to say that there is no requirements in Agile. Sprint (iteration) has all of phases that has waterfall.
    Are you sure you want to  Yes  No
    Your message goes here
  • What about the different level of prescription for different flavors of Agile? You know automation is normally so required in XP, but is not necessarily required by Scrum even when it's preferable.
    I mean, not all the projects had been designed to facilitate the automated testing and currently you have to test in the best way, but automation is not possible or is limited.
    So very probably, we can automate just a portion of the process and and we still be Agile. Even if we had the chance of automate everything, we cannot avoid manual testing and we shouldn't relieve us of the exploratory process that the 'Agile-Tester' prefers.
    Are you sure you want to  Yes  No
    Your message goes here
  • Slide 7 is not an explanation of the difference between Agile and Waterfall. Or are you trying to say that there are not requirements in Agile? not Design-Coding either? The difference is the short time we use to do the same things, and the approach for each activity, with focus in face-to-face work and interaction to rich the goals.
    Are you sure you want to  Yes  No
    Your message goes here

Agile Testing - presentation for Agile User Group

  1. 1. Agile Testing<br />Zbyszek Moćkun<br />
  2. 2. Agenda<br /><ul><li>QA and Testing
  3. 3. Agile Testing
  4. 4. Process, Tester Principles
  5. 5. Agile against Waterfall (differences)
  6. 6. Continuous Integration
  7. 7. Builds, Test Automation
  8. 8. Managing issues found by Automated Tests, Test Case Management
  9. 9. Is it worth?
  10. 10. Pseudo Agile projects
  11. 11. Mini waterfall, No automation
  12. 12. Agile only during development phase
  13. 13. From Waterfall to Agile
  14. 14. Tester-Developer cooperation
  15. 15. Tester concerns about Agile</li></li></ul><li>QA and Testing<br />What is a difference between QA and Testing?<br />QA is oriented to defect ‘preventions’<br />Testing is oriented to defect ‘detection’<br />
  16. 16. QA and Testing<br />QA<br />measure quality of process<br />Testing<br />gives metrics<br />
  17. 17. Agile Tester Principle<br />Provide continuous feedback<br />Deliver value to the customer<br />Enable face-to-face communication<br />Have courage<br />Keep it simple<br />Practise continuous improvement<br />Respond to change<br />Self-organize<br />Focus on people<br />Enjoy<br />Lisa Crispin, Janet Gregory – Agile Testing<br />
  18. 18. Agile Testing - Process<br />InitialPlanning<br />Release/New functionality<br />
  19. 19. Agile against Waterfall<br />Agile<br />Waterfall<br />Coding, newfunctionality<br />Bug fixing<br />Testing<br />Release<br />Iteration<br />
  20. 20. Agile Testing - Iterations<br />After each iteration we have finished stories and release is possible<br />Waterfall – allnewfeatures (A,B,C,D,E,F) availableatthe same time, attheend of theproject<br />
  21. 21. Continuous Integration<br /> 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.<br />Martin Fowler<br />
  22. 22. Builds<br />Continuous Integration<br />How to integrate builds with Automation Tests<br />When rebuild and run tests<br />
  23. 23. Test Automation<br />Tools (Selenium, Canoo Web Test, …)<br />Technology (Html vs. Java,C,..)<br />Who is reposnible for automation?<br />Integration with Continuous Integration applications<br />When start work on automation?<br />Reporting <br />
  24. 24. Manage Automation<br />When run Automation tests<br />Updating existing test scripts<br />Automation test scripts for different releases, clients<br />Creating new tests<br />What automate, what not?<br />Manage automation tests – Test Case Management Tools<br />
  25. 25. Managing bugs<br />How fast should we fix issues found by ATC?<br />Should we raise official issues?<br />Propagation issues for regression/UAT tests<br />
  26. 26. Manual Tests<br />How to manage manual and automation tests<br />Still we need manual testing?<br />When run manual tests<br />When testing stories<br />When testing bugs<br />Managing issues<br />
  27. 27. Test Case Management<br />How do not mixed up with tests<br />Why should we manage test cases<br />How do not duplicate tests<br />How report manual and automation tests<br />Integration with automation tool and defect managment tools<br />Test Case Managment tools <br />
  28. 28. Agile vs. Waterfall<br />Agile moves automation near development, which gives us less cost of fixing bugs<br />Waterfall problem - often builds don’t pass smoke tests. Thanks moving automation, it almost not happen at all.<br />QA in waterfall keep automaiton only for them<br />Less manual testing in Agile<br />
  29. 29. Is it worth?<br />Agile<br />Better for small projects<br />Moves automation near development (better use)<br />Better when good contact with customer<br />Require experience and trainings<br />New expirience<br />Waterfall<br />Big projects where requirement not change often<br />Easier in managment<br />Easier when team is located in different localizations<br />
  30. 30. Pseudo Agile Projects<br />Three examples of projects where Agile was introduce, but ... – from Tester perspective<br />
  31. 31. Miniwaterfall<br />Requirement<br />Requirement<br />Coding<br />Coding & Fixing<br />Coding<br />Coding & Fixing<br />Testing<br />Testing<br />Iteration 2<br />Iteration 1<br />
  32. 32. Miniwaterfall<br />Lack of automation tests<br />Lack of Continuous Integration <br />Complicated build system<br />Lack of Resource<br />
  33. 33. No automation<br />It usually provides to miniwaterfall, which we describe previously. <br />No releases after iteration, regression tests necessary<br />Long time period between releases<br />
  34. 34. Agile only during development phase<br />Only developers work in Agile<br />Just coding divided on iteratons<br />No tests during development<br />Automation (if exist) still stays on Test Team side<br />Waterfall project<br />Problems with builds from development<br />
  35. 35. From Waterfall to Agile<br />Few <br />Tester<br />Thoughts<br />
  36. 36. Tester – Developer cooperation<br />Agile<br />One project team<br />Close communication with developers (cooperate)<br />The same aim<br />Together analyze requirements, planning<br />Parreralworkwithdevelopers<br />Waterall<br />Different team<br />Mostly communication only by defect management tools<br />Different aims<br />Not involve in requirement analyzing, planning<br />Time delaybetweencoding and tests<br />
  37. 37. Tester concerns about Agile<br />Tester manage by developer (project manager) <br />Lost of identity<br />No defined task (self-organize)<br />No Agile training<br />No carrier path<br />Communication problem<br />
  38. 38. Tester concerns about Agile<br />Place in project<br />Development skills only<br />There is no Agile without automation<br />There is no QA (Test) department on Agile project<br />No exchange information between testers in different projects<br />How I can develop my career<br />
  39. 39. Q&A<br />