Ticket #217 (closed enhancement: fixed)

Opened 6 years ago

Last modified 5 years ago

Check install process runs unattended in kickstart install validation test case

Reported by: adamwill Owned by: rhe
Priority: major Milestone: Fedora 16
Component: Wiki Version:
Keywords: Cc:
Blocked By: Blocking:


As per the Beta criteria survey in https://fedorahosted.org/fedora-qa/ticket/151 , there is no test case to enforce the Beta release criterion "Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention)". The criterion is intentionally a bit open-ended so it may not be possible to enforce it exhaustively, but the most important scenario (and the one that prompted the criterion) is that of a kickstart install, which should run unattended as long as the .ks file doesn't somehow invoke something which unavoidably requires user interaction.

So, we could either have a new test case, or adjust one or more of the kickstart test cases to also check that the process completes unattended.

Change History

comment:1 follow-up: ↓ 2 Changed 6 years ago by rhe

  • Status changed from new to assigned

Agree. add a expected result in each kickstart test like:

comment:2 in reply to: ↑ 1 Changed 5 years ago by rhe

  • Status changed from assigned to closed
  • Resolution set to fixed

Replying to rhe:

Agree. add a expected result in each kickstart test like:

The added expected result is:
# Anaconda should not prompt for user interaction if ks.cfg is not specified

Feel free to adjust the words, closing this ticket for now.

Note: See TracTickets for help on using tickets.