Need new project in litmus.mozilla.org for testing bugzilla.mozilla.org during upgrades

VERIFIED FIXED

Status

VERIFIED FIXED
8 years ago
a day ago

People

(Reporter: dkl, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
I need a test case management tool for tracking manual test cases for testing bugzilla.mozilla.org during upgrades and other major changes. It would need to be it's own project or container and I would like to be able to create test runs of a list of test cases that can be passed or failed. 

A structure similar to the following would be nice:

BMO Customizations (test plan)
|
+--- BMO 4.0 Upgrade Beta 1 (test run)
     |
     +--- Test Case 1 (some manual test case)
     |
     +--- Test Case 2
     |

Is something like this possible with Litmus and would I be able to clone the test cases into another test run easily?

Thanks in advance
Dave

Comment 1

8 years ago
Hey Stephen, I hope you don't mind, but I went ahead and created the Bugzilla Product in Litmus.

Structure is as follows:
Bugzilla
|
+-- Bugzilla Basic Tests
    |
    +-- Bugzilla Bug View
        |
        +-- Test Case X
    +-- Some other bugzilla area (TBD)
        |
        +-- Test case Y
    +-- and so on

So, Litmus enforces this three tier hierarchy.  You have your product at the top level, I named that "Bugzilla" so that it matches the other products in litmus. At the next level you have your "Test Type" this is usually a specific type of test.  Here I've just made a testgroup called "Bugzilla Basic Tests".  I think that you'll only need one testgroup for what you're doing.

Within a testgroup, you have subgroups, this is for different parts of the product.  Like the "Bug View", "Search View" or however you organize your tests.  Your test cases live in these subgroups.  I made a silly test case so you can see it.  You can edit all these levels as a Bugzilla Product admin (if you log in with your mozilla.com address, you should have these privileges).

Test runs are a collection of testgroups that are being run at a specific time.  So your "BMO 4.0 Upgrade Beta 1" maps to a test run.  I made a "Bugzilla 4.0 Catch All Test Run" so you can see how all this stuff integrates together.

You can see it here:
https://litmus.mozilla.org/run_tests.cgi?test_run_id=250

Let me know if you have any questions.
(Reporter)

Comment 2

8 years ago
Thanks Clint. This should work well for my purposes and will give it a go for now. We can close this bug out as I have now what I need to get started.

Thanks again
Dave
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Clint, no worries; quite the contrary: thanks for taking care of this, since I kinda dropped the ball on getting it done for David.
Bumping to verified per comment 2.
Status: RESOLVED → VERIFIED

Updated

a day ago
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.