On this episode Matthew and Federico talk about how our team partitions the test bed by using priorities. They discuss why having an incremental automation test bed is important and how having a standarized meaning for priorities can help.
News:
- Microsoft Ajax Library Preview 6
- Welcome to our new team member Drew Miller.
Test case priorities
- Grouping tests by a common priority bar is useful when dealing with a big test bed.
- Pri 0
- A small number of positive tests under one configuration.
- Constitute 10-20% of a feature's tests.
- Regression amounts to a ship stopper.
- Pri 1
- Coverage for 80% of the use cases of a feature under multiple configuration.
- Constitue 80% of a feature's tests.
- Pri 2
- Edge or low impact scenarios.
- Constitute 10-20% of a feature's tests.
- Why do we need pri 0 functional tests if we already have unit tests?
- Your guidelines are ambiguous, how do you apply them?
Comments