https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/308 for openQA side.

The wiki test case is here https://fedoraproject.org/wiki/QA:Testcase_partial_kickstarts

If we care about it so much, we probably should have one.

Just a note, "partial kickstart" wasn't an important part of the decision, at least for me. Even in a fully automated case, not showing any display is a terrible behavior. On top of that, I believe I tested it with a fully automated test case, but it seemed like it stayed in the main menu (but I could only guess by the cursor changing shapes!), and I had no idea why, because it was all black. It just breaks kickstart installs completely, because you can't even develop and test your kickstart, since you get no visible output, no error messages, etc.

I don't mind having a specific test case for partial installs, of course. Just wanted to clarify the background.

@sumantrom I would prefer if you go with the name I proposed, because it follows the names of other kickstart tests better. There is no point in making "kickstarts" plural, either.

@adamw done. the new tc is https://fedoraproject.org/wiki/QA:Testcase_kickstart_partial

Thanks. So...

• The link to the sample kickstart is broken. Anyway, we don't really need a link to it there.
• Is the sample kickstart actually partial? At a quick glance, I don't see anything missing. What we mean by a "partial" kickstart is one that leaves some essential element of configuration out so that you must do it interactively - e.g. leave out the repository configuration, or the package set.
• Instead of having a link to the kickstart in the 'Setup' section and using an example URL in the 'How to test' section, I'd just do it the way https://fedoraproject.org/wiki/QA:Testcase_kickstart_user_creation does it - leave that out of the "Setup" section, and include the actual URL to the kickstart in the "How to test" section
• The rest of the "how to test" section doesn't really explain what is intended to happen correctly. It needs to explain that the install process should boot to the hub (graphical or text) and then prompt the user to fill out the incomplete required configuration, then once that is done installation should proceed smoothly.

The sample kickstart left out storage, so that it needed to be configured.