Test cases 8.2.1

Introduction

This is the test plan page for the 8.2.1 release. A large part of it is based on the tickets given in the ECO.

Mel Chua is the test manager for the 8.2.1 release; please contact Mel with any questions, criticisms, concerns, ideas, and test results you might have. The preferred way for doing so is emailing questions to the testing mailing list and ccing mel at laptop dot org.

Status

See the page on the role of a test manager for more information about these two questions.

• Are we done yet? 0 out of 17 tickets (0%) have been verified as closed in the release candidate build.
• What are the risks? The largest current risk is that we do not know potential areas of risk, but connectivity is a potential regression area. (This question will become more important as the answer to "Are we done yet?" gets closer to "we think so.")

Help unblock testers!

These are things we need - things that are actively blocking our ability to test the 8.2.1 release. If you can get us these resources, it would be a great help - if you clear a blocker, please email the testing mailing list and cc Mel (see #Introduction) so that we're all informed.

• We need a build to test! (And a way to get build announcements in the future - can announcements for builds that need testing be sent to the testing mailing list?)
• For each build we're expected to test, we need a build changelog that outlines the major differences between this build and the last one we've tested, so we know what to look at.

Things testers need to do

The next things that need to be done - I'm trying to turn these into tasks that people can pick up on more independently, but please shout on the testing mailing list if you'd like to help. I'd love to work with people to do this, and am willing to teach what I know about doing it (though I'm also figuring this out myself as we go along) Mchua 15:55, 24 December 2008 (UTC)

• Each ticket needs to be examined (talk with developers!) for areas of potential risk/exploration, and additional test cases for those areas should be added.
• The smoke test needs to be turned from 4 hours down into 1 hour through whatever means we can find, without reducing coverage. Automation tools, shortcuts, better instructions, ways of parallelizing the test... the burden of running a smoke test is currently Still Too High.
• Join the 8.2.1 triage meetings (time/location TBA, but they will be on IRC) led by Ed McNierney (8.2.1 release manager) to help answer the following questions on each 8.2.1 milestone ticket:
  • is it fixed?
  • is this the best way to fix that bug?
  • what are the potential regressions?

Tests

Smoke tests

Test results are not reported below. These are the tests that should be run on every build before it is listed as the build to test at Friends in Testing.

{{#ask: Test category::SmokeTest

Test case	Short name	Test objective	Add test result
?Short name	?Test objective	format=template	template=test-case-query	default=No articles found in Category:Test cases with Property:Test category of SmokeTest?! }}

Tickets for this build

Every test case that has a result for Property:Build stream 8.2.1 and also has a Property:Trac bug number — the ticket may be for a test result for a completely unrelated release!.

{{#ask:

 Build stream::8.2.1 Trac_bug_number::+
 | ?Build stream
 | ?Trac bug number
 | default=No test cases found for Property:Build stream 8.2.1 with a Property:Trac bug number !?

}}

Test results

Note! The values in the different columns are unrelated. Just because a build and "Fail" are on the same row doesn't mean that's the failing test result. You have to look at the original test case to see what values are from the same test result.

{{#ask: Build stream::8.2.1 |?Build stream |?Build number |?Trac bug number |?PassFail |default=Nothing in Category:Test cases found with Property:Build stream of 8.2.1?! }}