#107: writing a python test (modeled similarly to install.py)
--------------------+-------------------------------------------------------
Reporter: liam | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Resolution: | Keywords:
--------------------+-------------------------------------------------------
Comment (by liam):
jlaska mentioned that:
If we can automate the DVD
install using a mechanism similar to that used by the existing
install.py test, it might make our lives easier in the long run. What
makes this scalable is if we have a small number of custom install
scripts, but a large number of kickstart files to describe the tests.
If we break down the needs of each install test ... do they all have
similar needs? From what I can tell, each install test needs to ...
* Prepare the host environment
* Define a guest environment (# and type of disks, #nics etc...)
* Validate the install images
* Specify a kickstart file to direct the install
* Detect install progress (and timeout if needed)
* Validate installed system meets kickstart criteria
* Cleanup the guest environment
* What other needs do install tests have?
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/107#comment:3>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project