Badge description: You created a QA test case for a package!
QA test cases are created by packagers as well as package testers. Anyone with permissions to create and edit pages on the fedoraproject.org wiki can create a QA test case.
As their name suggest, they server for quality assurance purposes -- use case testing, regression testing, etc. As an example, here's a Firefox package test case:
https://fedoraproject.org/wiki/QA:Testcase_firefox_media
The test case are automatically linked to package updates in Bodhi ([https://bodhi.fedoraproject.org/updates/FEDORA-2016-0af3ff40a7 example]) where package testers can indicate whether the package passes a test case or not.
Because the test case page names have to follow specific naming conventions, it should be easy to create criteria for awarding the badge.
Ideas for artwork:
Maybe something like this: https://quickmvp.com/assets/icon-interview-de0dffca837a46addacdb776bfba852d.png with the package icon included on the paper
Interesting badge, I am more interested to know how this is going to get automated for awarding these badges.
Hi mildew, thanks for submitting this ticket. Like pnemade asked, I am also curious to know if this could be automated. I'm inclined to say probably not since it's creating wiki pages. However, it seems like creating a test case is a fairly significant task, right? So it should be possible for lead members of the QA team to remember to award this badge for people who create the test cases.
Some more context about the process for creating test cases would be helpful. One of my concerns with badges is that we have a lot of the manually awarded ones, but over time, people lose track of them and forget to award them for tasks like this, so I'd want to make sure that this is not too frequent or minor of a thing where it would become tedious or difficult to keep up with.
I think it will be fine if this badge is manually awarded, but I would want to both ensure that this is a notable task in the QA process and also probably identity some key members of the QA team to potentially assign awarding privileges for this badge so that there will always be an active member of QA who could award the badge.
Thanks!
Hi! I'm sending the badge. Please review. <img alt="481.png" src="/Fedora-Badges/issue/raw/files/2156019faf64595fcb97e10cfcd483a955f330f9cd809a5aa9e89b8490067187-481.png" /> <img alt="QA-481.svg" src="/Fedora-Badges/issue/raw/files/2bffca6722af66fbe939967a17bb963ed1c634fec6671679907d701a1a0e1bd0-QA-481.svg" />
Metadata Update from @mleonova: - Custom field concept_review_passed adjusted to on (was: 1) - Custom field has_description adjusted to on (was: 1) - Custom field has_name reset - Custom field needs_manual_award reset - Custom field triaged adjusted to on (was: 1) - Issue assigned to terezahl - Issue close_status updated to: None - Issue tagged with: bodhi, package, testing
Hey @mildew , what do you think about @pnemade and @jflory7 's comments?
Metadata Update from @mleonova: - Custom field has_name reset - Custom field needs_manual_award reset
I have no idea whether this can be automated as I don't have insight into the Fedora message bus internal and how the wiki is connected to it. However, the test case pages have to follow a certain naming scheme, so it should be possible to recognize a wiki edit from a test case edit.
The test case creation process is documented here: https://fedoraproject.org/wiki/QA:SOP_test_case_creation
Cannot answer that as I am not a member of Fedora QA. IMHO it is a notable task.
Metadata Update from @riecatnor: - Custom field artwork adjusted to has_draft - Custom field concept_review_passed adjusted to None (was: on) - Custom field has_complete_yaml reset (from None) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Issue tagged with: quality
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Issue tagged with: review
Closing this ticket due to inactivity during Badges virtual hackfest. Please reopen if their is renewed interest. Thanks!
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Issue close_status updated to: declined - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.