#202: Create test case for firstboot (graphic and text) ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- Per #151, we are missing test cases for firstboot functionality, which is required by Alpha release criterion "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account". We should create a test case to verify this requirement and add it to the matrices. Assigning to myself for now, but anyone else, feel free to jump in!
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by adamwill):
Created a test case, here:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
didn't add it to any matrix yet as this is not an installation or a desktop test, exactly. I think we should add a third matrix, which in my head at the moment is called 'base'...
On 06/23/2011 03:05 PM, Fedora QA wrote:
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by adamwill):
Created a test case, here:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
didn't add it to any matrix yet as this is not an installation or a desktop test, exactly. I think we should add a third matrix, which in my head at the moment is called 'base'...
I think it might make sense to include tests with and without a luks encrypted filesystem as well if possible - luks could be swap and/or /home or possibly root as well.
gene
On Thu, 2011-06-23 at 15:50 -0400, Genes MailLists wrote:
On 06/23/2011 03:05 PM, Fedora QA wrote:
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by adamwill):
Created a test case, here:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
didn't add it to any matrix yet as this is not an installation or a desktop test, exactly. I think we should add a third matrix, which in my head at the moment is called 'base'...
I think it might make sense to include tests with and without a luks encrypted filesystem as well if possible - luks could be swap and/or /home or possibly root as well.
That's outside the scope of this test: this test is specifically to test firstboot functionality. We already have a test case which tests encryption in the installer - https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(encrypted)_ins... . Though it's currently rather messily twinned with a keymap test, which was my stupid idea, which we should really clean up.
I had the new 'base startup' test cover unlocking an encrypted partition on boot: https://fedoraproject.org/wiki/QA:Testcase_base_startup
On 06/23/2011 04:02 PM, Adam Williamson wrote:
On Thu, 2011-06-23 at 15:50 -0400, Genes MailLists wrote:
On 06/23/2011 03:05 PM, Fedora QA wrote:
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by adamwill):
Created a test case, here:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
didn't add it to any matrix yet as this is not an installation or a desktop test, exactly. I think we should add a third matrix, which in my head at the moment is called 'base'...
I think it might make sense to include tests with and without a luks encrypted filesystem as well if possible - luks could be swap and/or /home or possibly root as well.
That's outside the scope of this test: this test is specifically to test firstboot functionality. We already have a test case which tests encryption in the installer - https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(encrypted)_ins... . Though it's currently rather messily twinned with a keymap test, which was my stupid idea, which we should really clean up.
I had the new 'base startup' test cover unlocking an encrypted partition on boot: https://fedoraproject.org/wiki/QA:Testcase_base_startup
Okidok whatever you think makes sense - but what I was thinking was that the luks password prompt can interfere with first boot if there is problem perhaps?
On Thu, 2011-06-23 at 16:26 -0400, Genes MailLists wrote:
Okidok whatever you think makes sense - but what I was thinking was that the luks password prompt can interfere with first boot if there is problem perhaps?
Oh, I see. That's true, yes, but it just feels better to me to have the firstboot test strictly to test firstboot functionality and have the encryption test separate. I guess as long as we have coverage for both things, exactly how they're organized isn't terribly important. A lot of the lines between what goes in what test case are pretty arbitrary.
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: assigned Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Changes (by adamwill):
* status: new => assigned
#202: Create test case for firstboot (graphic and text) -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: closed Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by adamwill):
* status: assigned => closed * resolution: => fixed
Comment:
This test case is now in the Base matrix. Closing.