we can see that cases whose link is not available in matrix. Some testers may ask how to test these cases,we need to complete them. https://fedoraproject.org/wiki/Test_Results:Fedora_12_RC4_Install
at least include these cases: * QA:Testcase_Mediakit_Repoclosure * QA:Testcase_Mediakit_FileConflicts * QA/TestCases/BootMethodsXenParaVirt * QA/TestCases/BootMethodsKVM * QA:Testcase Anaconda save traceback to remote system * QA:Testcase Anaconda save traceback to disk * QA:Testcase Anaconda traceback debug mode * QA:Testcase_Install_to_Pata_Device * QA/TestCases/UserInterfaceCmdline * QA/TestCases/UserInterfaceTelnet
completed cases: QA:Testcase_Mediakit_Repoclosure , QA/TestCases/BootMethodsXenParaVirt , QA/TestCases/BootMethodsKVM , QA:Testcase Anaconda save traceback to remote system , QA:Testcase Anaconda save traceback to disk , QA:Testcase Anaconda traceback debug mode , QA:Testcase_Install_to_Pata_Device , QA/TestCases/UserInterfaceCmdline , QA/TestCases/UserInterfaceTelnet
Please feel free to supplement and correct mistakes,For case: QA:Testcase_Mediakit_FileConflicts ,I did not find a appropriate way. To finish an installation with all packages selected, then check install process and /root/install.log file to see whether there are conflicts? I don't know this works or not. Do you have some good ideas about checking conflicts?
Changing title to reflect last remaining test case needing definition
I can take ownership of this ticket to handle this remaining test case. I'll try to post some feedback shortly.
Created https://fedoraproject.org/wiki/QA:Testcase_Mediakit_FileConflicts which uses the potential_conflict.py script that is included in autoqa.
Nice work Liam, I think this closes the loop on all the remaining test cases.
This ticket has been resolved.
Metadata Update from @adamwill: - Issue untagged with: test review - Issue tagged with: test cases
Log in to comment on this ticket.