Testcase management in Launchpad

Bug #211320 reported by Chris Gregan
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Feature Request:
Launchpad handles requirements, code, and defects well, but there is a missing area between these; Testing.

I would like to see a feature added at the same level as Blueprints, Bugs, Code, etc. The ability to create testcases in Launchpad by project and/or product would improve both internal canonical testing, as well as community testing.

The cases should have the ability to me linked to multiple projects, blueprints, and bugs.
Once linked, when changes are made to any linked resource, the case owner is notified.

Cases should have the ability to be searched by project, product, and keywords.

Cases should have the ability to be private.

Revision history for this message
Leo Arias (elopio) wrote :

This would be great. It should let you add step by step procedures to specify scenarios.
Those scenarios can be linked to the automation code (if the scenario is automated, of course). But I don't know how this can be handled as most of the automation code is included with the rest of the code.

Revision history for this message
Sivan Greenberg (sivan) wrote :

Note the tool I mentioned in my original blueprint linked from this bug. I'd like to see integration of its features together with the ability to link against the relevant objects in launchpad.

The nice feature of the mentioned tool is that test cases and suites can be the basis of further or larger test suites and are derivable, much like OO programming where you have a base class and its derivatives.

That would be useful to have since many of the components that are candidates for testing share functionality, data and so forth. In this regard I envision the case of a GNOME upstream creating a test case / suite for the software he maintains in Launchpad, and ubuntu qa team 'subclassing' this suite or individual test cases and adding/overriding specific tests or part of tests to make the resulting suite reflect the changes the distro team does to upstream packages.

Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Robert Collins (lifeless) wrote :

Is this about manual test plans, or automated test suites, or something else?

tags: added: feature
Revision history for this message
Leo Arias (elopio) wrote :

lifeless, what I would like is manual test plans. What we write now on http://testcases.qa.ubuntu.com/

As (I think) I suggested three years ago is that if some of the manual test have been automated, they should be linked to the code project somehow.

We also should have a way to define a test plan, and the testers executing the plan should be able to tell if the test succeeded or failed. And we should be able to see reports of the results.

Now, we could think that these documentations could be exported on a checkbox format. Or event better, this thing could be a web checkbox-editor[1] integrated into launchpad.

And, to finish the request of really cool things to have, the results of running the tests with checkbox should be easily imported into this.

[1] https://launchpad.net/checkbox-editor

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers