Agile Testing - presentation for Agile User Group

Uploaded 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.

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.

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • 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
    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
    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
    Your message goes here
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Agile Testing
    Zbyszek Moćkun
  • 2. Agenda
    • QA and Testing
    • 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
    • 15. Tester concerns about Agile
  • QA and Testing
    What is a difference between QA and Testing?
    QA is oriented to defect ‘preventions’
    Testing is oriented to defect ‘detection’
  • 16. QA and Testing
    measure quality of process
    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
    Focus on people
    Lisa Crispin, Janet Gregory – Agile Testing
  • 18. Agile Testing - Process
    Release/New functionality
  • 19. Agile against Waterfall
    Coding, newfunctionality
    Bug fixing
  • 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?
  • 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?
    Better for small projects
    Moves automation near development (better use)
    Better when good contact with customer
    Require experience and trainings
    New expirience
    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
    Coding & Fixing
    Coding & Fixing
    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
  • 36. Tester – Developer cooperation
    One project team
    Close communication with developers (cooperate)
    The same aim
    Together analyze requirements, planning
    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