What’s the difference between Severity and Priority?

Severity rates a defect in terms of its impact on the software under test (SUT) and/or on its environment; Priority (a.k.a URGENCY or CRITICALITY) rates it in terms of its impact on human stakeholders (the customer, users, developers, testers …).

A common (rather subjective) scale of SEVERITY goes like this (sometimes the numbers are reversed):

1. Critical - The defect results in the termination of the complete SUT or one or more component applications of the SUT (or of associated software such as the operating system), and/or causes extensive corruption of stored data. The failed function is unusable and there is no acceptable alternative method to achieve the required results.

2. Major - The defect results in the termination of the complete SUT or one or more component applications of the SUT (or of associated software such as the operating system), or causes extensive corruption of stored data; but although the failed function is unusable, there exists an acceptable alternative method to achieve the required results.

3. Moderate - The defect does not result in a termination, but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the systems usability.

4. Minor - The defect does not result in a termination, and does not impair usability, and the desired processing results are easily obtained by working around the defect.

5. Cosmetic - The defect is the result of non-conformance to a standard, is related to the aesthetics of the system, or is a request for an enhancement. Defects at this level may be deferred or even ignored.

PRIORITY will be partially based on Severity, but should take into account other factors such as the frequency with which the defect results in failure, the degree of “visibility” of failure (e.g., how many users it will affect, with what impact on their work, and whether it will be visible to external
customers), and project-related factors such as the impact on continued development or testing.

A commonly-used scale of PRIORITY reads:

1. Resolve Immediately - Further development and/or testing cannot occur until the defect has been repaired. The system cannot be used until the repair has been effected.

2. Give High Attention - The defect must be resolved as soon as possible because it is impairing development/and or testing activities. System use will be severely affected until the defect is fixed.

3. Normal Queue - The defect should be resolved in the normal course of development activities. It can wait until a new build or version is created.

4. Low Priority - The defect is an irritant which should be repaired, but repair can be deferred until after more serious defect have been fixed.

5. Suspend - The defect repair can be put off indefinitely. It can be resolved in a future major system revision or not resolved at all.

Define Test Scenario

Test Scenario: Test Scenario is the user workflow in the application.

Example: Checking Mail in Yahoo is a scenario, where user login, check the mail in inbox and then logoff. This application can have 2 different test case one for login and other one for inbox.

So Test Scenario can consist of different test cases.

How keep track of Test cases and Testing done by the testers

Believe in doing the right thing the first time...

Start creating the test wares based on the flow charts (or activity diagram) of the module you wish to test...

This flowchart must be approved by the R&D counterparts.

It is also recommended that you create an integration map of the module with other related modules. This will help you to develop the integration cases. So once you receive the release notes with a bug fix,you know which all integration cases you need to execute.

Traceability matrix is a very useful tool in case you need to keep track that none of the requirements are missed out while writing cases. The flow chart will ensure that none of the paths/scenarios are skipped out.

Maintain the cases in excel so that you can use formulas to track the cases written/executed and even the pass/fail statistics easily... Some of the useful columns for tracking purposes are date of execution,defect id (for failed cases), Requirement number, Test case id