Feature #279
Testing checklist for new releases
| Status: | New | Start date: | 02/16/2010 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | - | % Done: | 70% |
||
| Category: | Documentation | ||||
| Target version: | - |
Description
We need a checklist fo things that need to be tested whenever there is a new release. Something that can be printed and marked out once verified works.
For example:- Boot from cdrom
- run setup-alpine
- lbu commit to usb
- reboot and check it comes back
- lbu commit to encrypted apkovl with password
- reboot and check if comes back
etc.
For vserver we could have soemthing like: create vserver guest... test that it runs.
Some of the tests could be automated and run via virtual serial console in qemu, some of the should include run from real hardware.
Once we have a specification what to test we could find people to actually run the test for each release candidate.
Can be done on the http://wiki.alpinelinux.org site.
History
Updated by Michael Mason almost 2 years ago
Would we also want to put upgrade tests in this template?
Would you like a list of hardware this template has been tested on?
List of hardware that we would like to test a release on?
http://wiki.alpinelinux.org/w/index.php?title=Alpine_Release_Testing_Checklist
Updated by Natanael Copa almost 2 years ago
- % Done changed from 0 to 70
Michael Mason wrote:
Would we also want to put upgrade tests in this template?
Would be nice, but probably better to keep number of tests down initially and get a system for doing the tests.
Where does the tester fill in what he/she has tested?
Would you like a list of hardware this template has been tested on?
Yes, this would be nice.
List of hardware that we would like to test a release on?
I think we start without. Most testers will probably do it on virtual hardware. Boot from usb must be done on real though, since there are no virtual machine (that I'm aware of) that can boot from virtual usb bus.
Updated by Jeff Bilyk 11 months ago
I'd like to see this handled by some of the automated testing that Natanael and I have discussed recently (well, more like a month or two back), where we could have as basic .iso QA bootup via qemu and run the tests described in the initial ticket posting, and have the option of running some advanced tests with two qemu instances networked together to test some client/server things. However, I've yet to start on that...
Updated by Jeff Bilyk 8 months ago
Because of other work, I haven't had the time to start on this. Is it better suited to someone on the release team, since I won't realistically have time to look at it in the next couple months?