|
| QUALITY ASSURANCE |
|
| Traditional SDLC |
|
| Agile methodology |
|
| Advantage of Agile over traditional SDLC |
| |
| Agile Software testing process |
|
|
|
1) Conversational test creation
2) Coaching tests
3) Providing test interfaces
4) Exploratory learning |
|
| Conversational test creation |
|
1) Who should write tests
2) Defining test is a key activity that should include programmers and customer representatives
3) Don't do it alone |
|
| Coaching tests |
|
1) A way of thinking about acceptance tests
2) Turn user stories in to tests
3) Tests provide |
- Goals and guidance
- Instant feedback
- Progress measurement
|
| 4) Tests are specified in a format |
- That is clear enough that users/customers can understand
- That is specific enough that it can be executed
|
| 5) Specification by example |
|
| Providing test Interfaces |
|
1) Developers are responsible for providing the fixtures that automate coaching tests.
2) In most cases XP teams are adding test interfaces to their products,rather than using external test tools. |
|
| Test Interaction model |
|
|
|
| Exploratory learning |
|
Plan to explore the product with each iteration
Look for bugs,missing features and opportunities for improvement
we don't understand software until we have used it |
|
 |
