#368: reconstructe Fedora install test automation framework ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: autotest | Keywords: ----------------------+----------------------------------------------------- A new framework should be constructed to mapping the test cases and kickstart files, and it also should be easy for the users to contribute.
A big idea is that one text file will be used to map the test case names and kickstart files, and the kickstart files will be keeped in a directory, during test, the test will iterate all the kickstart in the directory. Users can create new kickstart files in the directory and write the relationship between test case and kickstart in the text file, of course, they can also pass it by arguments instead of doing this.
#368: reconstructe Fedora install test automation framework ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: assigned Priority: major | Milestone: Automate installation test plan Component: autotest | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by hongqing):
* status: new => assigned
#368: reconstructe Fedora install test automation framework ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: assigned Priority: major | Milestone: Automate installation test plan Component: autotest | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by hongqing):
Each test case has a corresponding kick start file, the framework should schedule each test case as a job, so it will be easy to monitor test progress and process the test results.
#368: reconstructe Fedora install test automation framework ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: assigned Priority: major | Milestone: Automate installation test plan Component: autotest | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by kparal):
Just a note: This could be much easier once we deploy ResultsDB, because you will be then able to start independent phases and report individual results in a single run. So it can then run as a single test run, that will perform 5 different installations using 5 different kickstart files and report it separately as 5 results.
#368: reconstructe Fedora install test automation framework ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: assigned Priority: major | Milestone: Automate installation test plan Component: autotest | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by hongqing):
Each test case may contain kick start file and kernel boot argument, it is not good to classify categories with directories, and it is trouble to match the category, test case and kernel boot arguments. So it would be better to store them in database. the attachment is a sample entity relationship diagram for this. [[BR]] category include: DVD,Live, General etc.[[BR]] repo: store repo loction, http, ftp, nfs etc.[[BR]] ask_method: specify askmethod will be passed to kernel terminal or not[[BR]] kick_start_type: remote, file, hd etc. kick_start: the kick start
autoqa-devel@lists.fedorahosted.org
-
fedora-badges