Agile Testing Process   Process Overview
Software development methodology   <ul><li>Agile – iterative development methodology, where requirements evolve through co...
Wrong ways of using a tester   <ul><li>A tester is not the one who can not program and causes breaks only. </li></ul><ul><...
Why teams switch to Agile   <ul><li>Simplicity of principles and apparent easiness of their employment. </li></ul><ul><li>...
Problems of switching to Agile <ul><li>Difficulty of leaving the traditional understanding of roles. </li></ul><ul><li>Res...
Adequate approach to a tester <ul><li>A tester is a team member! </li></ul><ul><li>The tester’s experience in development ...
Changes in testing <ul><li>Start of a sprint – start of testing. </li></ul><ul><li>Testing activities are the same as in o...
Types of testing <ul><li>Test planning. </li></ul><ul><li>Build acceptance testing. </li></ul><ul><li>Functional testing. ...
Off-testing time   <ul><li>Analysis of requirements and risks; test planning. </li></ul><ul><li>Test automation . </li></u...
Problems with testing shortage   <ul><li>Lack of testing resources . </li></ul><ul><li>Inefficient test planning . </li></...
Ways of problem solving   <ul><li>Detailed test planning. </li></ul><ul><li>Automation, possibly with the developers’ help...
Benefits of being an Agile testers <ul><li>Less risk of  compressed  test period. </li></ul><ul><li>Test all the time, not...
Upcoming SlideShare
Loading in...5
×

Agile Testing Process

59,307

Published on

Published in: Technology
3 Comments
20 Likes
Statistics
Notes
No Downloads
Views
Total Views
59,307
On Slideshare
0
From Embeds
0
Number of Embeds
29
Actions
Shares
0
Downloads
1,315
Comments
3
Likes
20
Embeds 0
No embeds

No notes for slide

Agile Testing Process

  1. 1. Agile Testing Process Process Overview
  2. 2. Software development methodology <ul><li>Agile – iterative development methodology, where requirements evolve through collaboration between the customer and self-organizing teams. Agile business approach aligns development with customer needs. </li></ul>
  3. 3. Wrong ways of using a tester <ul><li>A tester is not the one who can not program and causes breaks only. </li></ul><ul><li>Inadequate use of the person’s potential and experience. </li></ul><ul><li>A tester does not participate in planning. </li></ul><ul><li>A tester’s work starts after the functional development. </li></ul>
  4. 4. Why teams switch to Agile <ul><li>Simplicity of principles and apparent easiness of their employment. </li></ul><ul><li>More transparent communication with the customer and accurate planning. </li></ul><ul><li>Agile is in fashion . </li></ul><ul><li>Examples of other teams . </li></ul>
  5. 5. Problems of switching to Agile <ul><li>Difficulty of leaving the traditional understanding of roles. </li></ul><ul><li>Resistance to changes . </li></ul><ul><li>In the adaptation phase the basic Agile principles may be destroyed. </li></ul><ul><li>Agile is not a panacea to solve all the problems. Agile principles just reveal the problems, and it is people who are to solve them. </li></ul>
  6. 6. Adequate approach to a tester <ul><li>A tester is a team member! </li></ul><ul><li>The tester’s experience in development should be fully used. </li></ul><ul><li>The tester’s functions are largely determined by the tester himself. </li></ul><ul><li>Participation in planning and requirements analysis. </li></ul>
  7. 7. Changes in testing <ul><li>Start of a sprint – start of testing. </li></ul><ul><li>Testing activities are the same as in other methodologies. </li></ul><ul><li>Testing tasks – usual sprint tasks. </li></ul><ul><li>All the team is responsible for the result, including quality. </li></ul><ul><li>Testing tasks – common tasks of all the team. </li></ul><ul><li>Maximum communication . </li></ul><ul><li>Provide continuous feedback. </li></ul><ul><ul><li>To the customer. </li></ul></ul><ul><ul><li>To the programmers. </li></ul></ul>
  8. 8. Types of testing <ul><li>Test planning. </li></ul><ul><li>Build acceptance testing. </li></ul><ul><li>Functional testing. </li></ul><ul><li>Regression testing. </li></ul><ul><li>Demo testing. </li></ul><ul><li>Test automation. </li></ul>
  9. 9. Off-testing time <ul><li>Analysis of requirements and risks; test planning. </li></ul><ul><li>Test automation . </li></ul><ul><li>Setting up test environments. </li></ul><ul><li>Preparing the necessary documentation . </li></ul><ul><li>Work with external resources . </li></ul><ul><li>Providing help to developers . </li></ul>
  10. 10. Problems with testing shortage <ul><li>Lack of testing resources . </li></ul><ul><li>Inefficient test planning . </li></ul><ul><li>A lot of manual testing. </li></ul><ul><li>Inefficient testing process . </li></ul><ul><li>Increasing functional for regression testing. </li></ul>
  11. 11. Ways of problem solving <ul><li>Detailed test planning. </li></ul><ul><li>Automation, possibly with the developers’ help. </li></ul><ul><li>Increased unit test code coverage. </li></ul><ul><li>Implementation of stabilization sprints. </li></ul><ul><li>Increase in the amount of testing resources. </li></ul>
  12. 12. Benefits of being an Agile testers <ul><li>Less risk of compressed test period. </li></ul><ul><li>Test all the time, not just at the end. </li></ul><ul><li>Work together as one team towards a common goal. </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×