To Provide a functional Spin, Testing is essential and critical to our spin :
We're going to be defining some specific criteria that needs to be passed in order for the spin to roll out.
We have setup a HackMD pad to discuss what needs to be Tested: here
We would have to document the raw test cases from the HackMD pad (into clear and concise steps) to mention them in the Change Proposal and For the Participants of the Test Days / Test Weeks to follow along with.
Our Docs repository lives: here We can create a new Tests Module and create a section for Testers.
@defolos will be working on Automating them with OpenQA
Metadata Update from @jflory7: - Issue assigned to defolos - Issue marked as blocking: #4
Are the examples given on the wiki draft of the Change Proposal sufficient for this ticket?
https://fedoraproject.org/wiki/SIGs/i3/SpinChangeProposal_Draft#How_To_Test
Metadata Update from @jflory7: - Issue marked as blocking: #4
We followed up on this in earlier meetings. The test cases we have written for the Change proposal are sufficient.
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.