Testopia and Bugzilla

Accessing Testopia

Any Bugzilla user can access Testopia by clicking on the "Product Dashboard" inside the main Bugzilla page

Products

The products in Testopia are imported from Bugzilla and are basically the products of the Yocto Project. These products can be seen in the left column of Testopia main page:

By clicking on a product you will see detailed description about it like the Test Plans it contains, the test cases and so forth.

---

Test Plans

• test plans are unique to the product they belong to and can not be shared between products.
• test plans contain all the test cases relevant to the product they belong to.

Test Cases

• test cases can not be shared between products.
• test cases can be shared between test plans within the same product.
• test cases have 2 special fields assigned to them: priority and category.
• test case priorities are linked to Bugzilla and affect bugs filed from the test case.

Test Runs

Test runs hold the results of how certain test cases fared in a specific build and environment. They are composed of Case Runs.

• test runs are unique to a specific product.
• test runs can not be shared between products.
• test runs are unique to the test plan they belong to.

Bug Life Cycle States:

• New - Potential defect that is raised and yet to be validated.
• Assigned - Assigned against a development team to address it but not yet resolved.
• Verified - The Defect that is retested and the test has been verified by QA.
• Closed - The final state of the defect that can be closed after the QA retesting or can be closed if the defect is duplicate or considered as NOT a defect.
• Reopened - When the defect is NOT fixed, QA reopens/reactivates the defect.

Bug Severity stages: 

Severity	Definition
blocker	Prevents function from being used, no work-around, blocking progress on multiple fronts
critical	Prevents function from being used, no work-around
major	Prevents function from being used, but a work-around is possible
normal	A problem making a function difficult to use but no special work-around is required
minor	A problem not affecting the actual function, but the behavior is not natural
trivial	A problem not affecting the actual function, a typo would be an example

Bug Priority levels:

• Urgent: Must to be fixed before any other high, medium or low defect should be fixed. Must be fixed in the next build.
• High: Must be fixed in any of the upcoming builds but should be included in the release.
• Medium: should take precedence over low priority defects and may be fixed after the release / in the next release.
• Low: Fixing can be deferred until all other priority defects are fixed. It may or may not be fixed at all.