#150 Testing days participation
Opened 5 years ago by zdenek. Modified 9 months ago

What the badge should be granted for:
- for submitting testing results on Wiki during Fedora test days.

Badge description (like "You added a co-maintainer to a package. BFF!"):
- I proudly support Fedora test days

Anything else we need to know:
- if possible, could be split to several classes based on effort given to test participation (e.g. differ between 1 submit, more and lots of submits)

or

  • to make the badge collection more competitive and interesting, there could be specific badge(s) for each test day (e.g. one has to participate in all test days to get whole Test Days badges collection)

Now that we have the [https://fedoraproject.org/wiki/QA:TestdayApp?rd=User:Jskladan/Sandbox:TestdayApp TestDay App] maybe it could hook into that.

I'd been thinking this could be one separate badge for each Fedora release (e.g. "I proudly support Fedora 20 test days"), and/or a set of counter badges for total {{{TestDay App}}} submissions.

+1, especially if we can hook in to the TestDay app.

Do we have any update on this trac?
I am planning for test day invite blog.
If this can be done, I can mention about this badge to attract more audience

Any ideas for artwork? I'd like to help out with a design

Possible artwork concepts: Room of badgers & pandas taking a test(it would be cute to include one trying to cheat). A series could be a test paper with a circled A+, B, C, D, & F on front.

Here is an idea for the artwork. @mleonova, thoughts? Do we want to add in numbering for specific releases? Or do we want just this one badge for participating in any test day? @amsharma @zdenek @twaugh
testday.png
testday.svg

Metadata Update from @riecatnor:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None (was: 0)
- Custom field has_complete_yaml reset (from None)
- Custom field has_description adjusted to on (was: 1)
- Custom field has_name adjusted to on (was: 1)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged reset (from 0)
- Issue close_status updated to: None

a year ago

I think it's pretty cool! Do you think we could add some more elements to the test itself, something like this?

Metadata Update from @mleonova:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

a year ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

a year ago

I think it looks great!

Metadata Update from @mleonova:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

a year ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to approved (was: None)
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

a year ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue tagged with: artwork-approved, quality

a year ago

Metadata Update from @sayanchowdhury:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue tagged with: not-yet-possible

9 months ago

Login to comment on this ticket.

Metadata
Attachments 4
Attached a year ago View Comment
Attached a year ago View Comment
Attached a year ago View Comment
Attached a year ago View Comment