DeveloperWiki:testplan
From ArchWiki
Use this plan to test as many things in as little testruns as possible:
Contents |
bugsquashing
image bootup
- if (you have a chipset for which there is a USB storage sub-driver module): check if boots [1]
- check if root directory patch works [2] and [3]
installation procedure
- consider doing an net install to test that everything works after renaming ftp to net [4] <--works
- if (manual network setup): use any IP with at least one of the bytes different from the default one or with more than 8 digits and check resulting broadcast ip (also check this in the configure system step in rc.conf) [5]
- check if setting clock makes sense [6].
- in partition editor: see what 'cancel' does, and try making nothing but a swap filesystem [7]
- package installation: if(ftp install): check if pacman works (no broken proxy settings) [8]
- if (ftp install): installer asks to include network settings at end of package installation? not before configure system? [9]
- configure system: if(encryption || lvm): check if we tell user to update HOOKS in rc.conf and kernel lines in grub menu.lst[10]
- at the end of configure system, after base locales generation: try to see if there is no error (appears very briefly) about /etc/localtime missing [11]
- grub installation: if(raid1): check if grub installs fine [12]
on final system
- if(encryption): try booting the livecd again and see if it bails out. [13]
- check if clock is still okay and you get no fsck errors "filesystem last used in the future" [14].
specific tests
grub refactorings
- manual install autoprepare. ??
- manual install manual setup lvm on crypt. HOOKS ok, menu.lst default (needs retest). boot?
- automatic example generic. ALL OK
- automatic example fancy. ALL OK
- test automatic-lvm-dmcrypt-install-sda: HOOKS ok, menu.lst ok. boots
- test automatic-dmcrypt-lvm-install-sda: device that hosts / does not seem to come online when booting (even though decrypt unlock worked)
- test automatic-reuse-fs-sda: ??