435402 - Add Weave as a new product to Litmus

Status: VERIFIED FIXED

(Webtools Graveyard :: Litmus, defect)

Description

[Tracy Walker [:tracy]]

Dan Mills has asked that we add a new product for Weave testing.  I've added him as a Super Admin.  Please add the product and I'll help him get Testgroups and Subgroups setup.

Comment 1

[Zach Lipton [:zach]]

I've created a Weave product and added a 'Trunk' branch to the product. Thanks for helping Dan get set up; let me know if you guys have any questions or need anything else created.

Tracy: I'm happy to do this, but know in the future that you can create products/branches yourself if you need to under "manage categories."

Comment 2

[Tracy Walker [:tracy]]

Thanks Zach.  

you can create products/branches yourself if you need to under "manage categories."
I didn't know that. Cool man.

Dan, I'm out for the weekend. But let me know if you need any help getting testgroups and subgroups added and organized correctly.

Zach, how does one add the product to the list on the test run page?

Comment 3

[Zach Lipton [:zach]]

(In reply to comment #2)
> you can create products/branches yourself if you need to under "manage
> categories."
> I didn't know that. Cool man.
You'se got the power man!

> 
> Dan, I'm out for the weekend. But let me know if you need any help getting
> testgroups and subgroups added and organized correctly.
I'll be out the rest of the day and traveling most of the weekend, but I'll be in periodic email contact. 

> Zach, how does one add the product to the list on the test run page?
Once you have your testgroups/subgroups/testcases all setup under the Weave product, go into the Manage Test Runs page and Add a New Test Run. The interface is rather more confusing than it ought to be, but the general idea is to create a "Weave Catch-all Test Run" with an ending timestamp far off into the future. You need not set any test run criteria unless you want to restrict the configurations that can access the run. Then just add your Weave testgroups to the run and save, and your tests will appear in the test run list. 

Later, you can create separate shorter-lived runs for different circumstances, say, a test run for testing prior to a release, and use the test run reporting tool to get coverage and results data for that specific run.

The admin tutorial is located at: http://quality.mozilla.org/howto/litmus/admin-tutorial

Comment 4

[Dan Mills [:thunder]]

Thanks! I'll start adding test cases right away.

Comment 5

[Chris Cooper [:coop] (he/him)]

(In reply to comment #3)
> The interface is rather more confusing than it ought to be

How, exactly? Bugs are better than random gripes.

I also don't think the interface is particularly difficult, but we've never trained anyone on how to use Litmus, we just expect them to "get it." Maybe a Litmus admin session at the summit would be useful.

Comment 6

[Zach Lipton [:zach]]

(In reply to comment #5)
> (In reply to comment #3)
> > The interface is rather more confusing than it ought to be
> How, exactly? Bugs are better than random gripes.

Sorry; that was rather snippy of me. I guess my point really was that the interface, as viewed by a new admin, seems to me rather overwhelming. Maybe a bit more contextual help around the "manage test run criteria" section would help clarify that area, as it's not obvious how that affects the test run report. It might also be nice to group test runs by product in the selection box at the top of the form, and maybe make the date format a little more readable with hyphens or the like. All pretty minor cosmetic things really, and hardly a priority on an admin page.

Also, I just noticed that the help link at the bottom seems to be broken, at least on my trunk nightly. I'll file a bug and look into this in a little bit.

> I also don't think the interface is particularly difficult, but we've never
> trained anyone on how to use Litmus, we just expect them to "get it." Maybe a
> Litmus admin session at the summit would be useful.
Hmm, that's a really good point. A walkthrough of the admin tools could be useful, especially for litmus users/potential users from outside of the QA team who may not use the admin pages that often.