Answered Questions

  • Why do we need testers not developers for testing?

  • Priority and Severity Examples

    Can some one give the best example for the following scenario's1. High Priority and high severity2. High Priority and low severity3. High severity and low priority4. low severity and low priority

    Star Read Best Answer

    Editorial / Best Answer


    • Member Since Dec-2007 | Mar 3rd, 2008

    Priority - Priority is the order in which developer has to fix the bug.
    Severity - Severity is how seroisly the bug is impacting the application.


    High Priority & High Severity: A show stopper error which occurs on the basic funcationality of the application . (Eg. A site maintaing the student details, on saving record if it, doesn't allow to save the record then this is high priority and high severity bug.)

    High Priority & Low Severity: The spell mistakes that happens on the cover page or headin or title of an application.

    High Severity & Low Priority: The application generates a show stopper or system error, (for which there is no workaround) but on click of link which is rarely used by the end user.

    Low Priority and Low Severity: Any cosmetic or spell issues which is with in a paragraph or in the report (Not on cover page, heading, title).

    Plz correct me if i am wrong.

    William Lodge

    • Sep 30th, 2015

    Could also have Low Severity with High Priority: e.g., Misspelling of company name on title page. Very embarrassing.

    Tahemeena Gunjarge

    • Apr 14th, 2015

    1)High Severity and Low priority --> application doesn't allow customer expected Configuration. 2)High severity and High priority -->Application doesn't allow multiple users. 3)Low severity and High...

  • how to test Maintenance project and what is the difference between the Maintenance project and project?