Test Case Prioritization

P1: The basic function of the system, the number of case should be controlled
Partitioning: Failure of this use case can result in multiple important functions being unavailable, high probability of occurrence, frequently used functions
This type of use case needs to be executed in each release test

P2: Important function of the system, more case number
Classification basis: A variety of application scenarios, the use of high frequency of normal functions. Functional interaction.
All important functions of the system must be implemented in the non-regression system test version.

P3: The general function of the system, a large number of case
Division by: Usage frequency is lower than P2, such as super long string, boundary value, thing integrality, etc.
Non-regression system test versions do not have to be validated, and in the middle and late of system testing, each version is not necessarily validated

P4: Optional
Division basis: More uncommon input, the use of very low frequency function
In the version test, there are some normal reasons, after the communication with the Product manager to confirm can not be executed

Ext.: http://onemonth.iteye.com/blog/2005790

Test case prioritization (GO)