On Mon, Dec 05, 2011 at 04:24:19PM +0000, Gema Gomez wrote: > Dear QA Team, > > as promised, here it is a list of tasks that need to be done and we are > in the process of doing that you could own if you have the time: > > - ISO testing tasks > (https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing): > > 1) Compile a list of applications that are installed by default by the > ISO installers (one for Desktop, one for Server) and propose two or > three basic test cases that could be run post install giving us basic > confidence that the ISO is good for further testing (i.e. compile a list > of post-install smoke tests that we could run with Jenkins). > - This task is not about generating code, but about thinking of what > packages of the ones installed are important and worth testing in a > daily test suite. We could split it in different tasks for different > people if we generate first a list of apps that we can use for the > generation of test cases. > 2) We need to fix the existing test cases in the tracker and convert > them to a better, more understandable format. Basically we need to > convert them to unambiguous and meaningful test cases. Some of them are > redundant, some of them are too long to be just one test case, some > others do not make sense anymore. This is a tidy up task that needs to > be done. > > - Metrics > (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics): > 3) I have some tasks here that could use some help. We need to look at > the codebase of Ubuntu main and see how to instrument the code so that > we can start generating code coverage metrics. This is about compiling > the Ubuntu code with gcov and generating binaries that can be used > (still to be seen how to install them) for this end. > - This task requires code in-depth knowledge and familiarity on how > things are built and can be changed to build in a different way. We > should decide where to start instrumenting and why. > > 4) Look into how to do test escape analysis with launchpad. TEA is an > analysis that will tell us, after Precise, if we missed some problems > that were found by someone after we did our testing and that should help > us understand whether we should be adding new test cases in those > "missed" areas or not. > > 5) Gather test cases from defects. This is about making a list of > defects that have been fixed for Oneiric and that have a set of steps to > reproduce the problem that needs to be gathered and written into a > proper test case.
Here are some Launchpad searches that should help: Bugs with an oneiric task that are Fix Released and have been tagged 'testcase'. https://bugs.launchpad.net/ubuntu/oneiric/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.tag=testcase&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Bugs about Ubuntu that are Fix Released and tagged 'testcase' and 'oneiric'. This one is timing out and causing an OOPs although it would be easy to get a list of the same bugs using the Launchpad API. https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.tag=oneiric+testcase&field.tags_combinator=ALL&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search My bug bot automatically tags bugs with the words "TEST CASE" in the description 'testcase' and has been doing so for some time now. -- Brian Murray -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
