QA In Agile: solutions

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

Favorites, Groups & Events

QA In Agile: solutions - Presentation Transcript

  1. QA in Agile Alimenkou Mikalai mailto:lumii.subscriber@gmail.com 28.06.2008
  2. QA Activities
    • Required
      • Regression testing
      • Iteration/release tasks testing
    • Optional
      • Release/demo management
      • Documentation management
  3. Regression Testing
    • Goals
      • Verify existing functionality
      • Check new integration points
      • Show and monitor project status
      • Check existing documentation
  4. Regression Testing
    • Issues
      • Functionality is growing too quickly
      • Not enough QA engineers
      • Too much manual work
      • Setup and configuration issues
      • Testing without plan/structure
  5. Iteration/Release Tasks Testing
    • Goals
      • Check new functionality
      • Show iteration/release status
      • Update/create documentation
  6. Iteration/Release Tasks Testing
    • Issues
      • Too many bugs in implemented tasks
      • Not enough time to the end of iteration
      • Regression testing is not finished
      • Tasks are too large
      • Long feedback/bug-fixing loop
      • QA work is not included in ‘DONE’ criteria
      • Switching of environments
  7. Release/Demo Management
    • Issues
      • Full regression is not finished
      • Bug fixes produces new bugs
      • Release/demo is prepared in the next iteration
  8. Documentation Management
    • Issues
      • No documentation at all
      • Documentation is hard to maintain
      • Too much time is spend for documentation
      • Documentation is not up to date
      • Documentation is not shared
  9. Common Issues
    • QA team is not collocated with developers
    • QA team members are part-time
    • Developers defend their code from QA
    • QA team don’t share project interests
    • QA tools minimize face-to-face interaction
    • Lack of respect for QA work
    • QA team is not enough skilled
  10. QA Iteration 1 2 4 3 6 5 8 9 7 10 days Phase I: Planning Phase II: Automated Acceptance Testing Phase III: Stories Testing Phase IV: Regression Testing Phase V: Demo
  11. Phase I: Planning
    • Goals
      • Complete understanding of sprint scope
      • Prioritization of tasks in the sprint
      • Additional point of view on stories
      • Increasing team collaboration
    • Best practices
      • Full QA team take part in planning
      • QA team members estimate stories
      • Some time at the end of iteration is reserved
      • QA estimations are used to order tasks
      • Both manual and automated tests are estimated
  12. Phase II: Acceptance Testing
    • Goals
      • Document new functionality
      • Prepare tests for ATDD
      • Decrease time for regression testing
      • Automate ‘DONE’ criteria
    • Best practices
      • Don’t use too technical tools
      • QA writes test, developer writes fixture
      • Test stories at the top of sprint backlog
      • Organize tests as documentation
      • Developers help QA to prepare tests
      • Completely automated testing environment
  13. Phase III: Stories Testing
    • Goals
      • Complete ‘DONE’ criteria
      • Integrate and check new functionality
      • Early preparation to the demo
    • Best practices
      • Use branches for large tasks or demo branch
      • Reduce amount of manual testing
      • Start story testing as soon as possible
      • Update test suite for bugs and issues
      • Completely automated testing environment
      • Developers often integrate code on local machines
  14. Phase IV: Regression Testing
    • Goals
      • Check integration of all implemented stories
      • Preparation to the demo
      • Prepare sprint status
    • Best practices
      • Division of automated tests in suites
      • Easy and short stories at the end of sprint
      • Buffer for team internal tasks
      • Developers help to perform testing
      • Some kind of code freezing
      • Categorization of bugs and issues
      • Update project testing metrics
  15. Phase V: Demo
    • Goals
      • Demonstrate implemented functionality
      • External demo
      • Share project knowledge and experience
    • Best practices
      • Prepare to the demo during sprint
      • Include demo preparation in ‘DONE’ criteria
      • Automated environment for demo
      • All team members present at the demo
      • Demo is driven by QA team member
      • Fixed time and place for sprint demo
  16. Phase VI: Retrospective
    • Goals
      • Share knowledge about QA process
      • Analyze and improve QA process
      • Increase integration with developers team
      • Analyze team structure
    • Best practices
      • Use external facilitator
      • Members of other teams present
      • Gather and share project metrics
      • Use experience of developers team in retrospectives
  17. Best Practices
    • Use engineer practices
      • Unit testing
      • TDD
      • ATDD
      • Continuous integration
      • Code review
      • Pair programming
      • Static analysis
  18. Best Practices
    • QA team is collocated with developers
    • Product owner works with QA for AT
    • At least 1 QA for each 2 developers
    • Increase QA team incrementally
    • Developers help with all technical stuff
    • Use short internal iteration before release
    • Calculate and publish testing metrics
    • Provide traceability for tests

+ krivitskykrivitsky, 2 years ago

custom

1301 views, 0 favs, 2 embeds more stats

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 1301
    • 1166 on SlideShare
    • 135 from embeds
  • Comments 1
  • Favorites 0
  • Downloads 45
Most viewed embeds
  • 84 views on http://www.agileukraine.org
  • 51 views on http://451f.com.ua

more

All embeds
  • 84 views on http://www.agileukraine.org
  • 51 views on http://451f.com.ua

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories