Hi, folks. So now we revised the release criteria for initial-setup and anaconda user creation instead of firstboot, we need to do the same for test cases. I'm proposing a couple of new test cases to replace https://fedoraproject.org/wiki/QA:Testcase_base_firstboot : https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_base_initial_setup https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_anaconda_user_creation One is a generic test for 'initial setup' type utilities, the other covers user creation in the installer. I'm envisaging that we can put them in the Base validation matrix with GNOME, KDE and Minimal columns to cover the three release-blocking installation types. That should cover all the possible paths through install and 'first boot' on our three release-blocking package sets. Note that, as written, the first test case can actually apply to ARM: 'deploying' ARM via a non-installer image would comply with the 'setup' and 'how to test' steps as they are described, and the test case would imply that user creation must work during first boot of a non-installer deployed ARM system, which I believe is desired. There would also need to be minor changes to https://fedoraproject.org/wiki/QA:Testcase_base_startup to go with this change, which should be pretty obvious. Anyone have comments/criticisms/questions/suggestions on the test cases themselves or this plan? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
