[Fedora QA] #154: Tracker: critical path test case creation
by fedora-badges
#154: Tracker: critical path test case creation
-------------------------+--------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
= problem =
We need more specific per-package guidance for proven tester testing, to
make sure the testing covers all the relevant critical path functionality
of each package.
= enhancement recommendation =
We can create a group of test cases in the Wiki for each critical path
package. Bodhi could integrate with this system and, in the future non-
numeric karma system, provide checkboxes for each test case for packages
which have test cases available. fedora-easy-karma could provide an
interface to display and check off test cases from the Wiki.
This ticket can serve as a tracker for this process, which will be
ongoing. To start with I will file tickets for each package which has so
far been identified (on test and devel mailing lists) as an obvious
candidate for such test cases, with a note of what should be covered for
each package. Those tickets will block this one.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/154>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #80: Add dual-boot release criteria
by fedora-badges
#80: Add dual-boot release criteria
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
See [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=590661
RHBZ#590661 - GRUB bootloader should have a few seconds delay on a multi-
boot setup]
= analysis =
Due to RHBZ #590661, the dual-boot experience was not well understood and
tested for the final release. It was discovered late and unclear whether
this behavior was critical to Fedora success.
= enhancement recommendation =
The user experience of dual-boot scenarios was not well understood, as a
result RHBZ #590661 did not clearly impact the release criteria.
Recommend reviewing and making adjustments to the release criteria for
dual-boot expectations.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/80>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #93: Review options to reward key QA contributors
by fedora-badges
#93: Review options to reward key QA contributors
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: jlaska
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
During Fedora 13, a small amount was available to reward several key QA
contributors for their efforts.
= analysis =
If possible, I'd like to repeat this in Fedora 14.
= enhancement recommendation =
What's the best way to say thanks?
1. Request and secure QA budget to reward key contributors
2. Researching reward options (maxamillion has discussed t-shirt ideas
with the design team)
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/93>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #89: Improve tracking blocker review status
by fedora-badges
#89: Improve tracking blocker review status
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: poelstra
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
Several bugs were changed so they fell off the tracking lists for Fedora
13. For example...
* [http://bugzilla.redhat.com/505189 505189 - Going back to repo UI
screen and and modifying Installation Repo causes traceback]
* [http://bugzilla.redhat.com/577803 577803 - Adding repository
requiring network fails if network is down]
= analysis =
In F-13, a bugzilla keyword was used to denote blocker status. However,
aside from reviewing bugzilla comments, there was no query-able method to
determine whether a blocker request is open, approved or denied. This led
to several Fedora 13 bugs that were 1) fixed in Rawhide, 2) Moved to
MODIFIED or CLOSED and not included, but not included in Fedora 13 (e.g.
RHBZ #505189 and RHBZ #577803).
Not knowing which bugs were already reviewed, also introduced time wasted
reviewing previously reviewed bugs during blocker review meetings.
= enhancement recommendation =
Recommend reviewing process changes to avoid the scenarios leading up to
RHBZ #505189 and RHBZ #577803. Some options discussed so far include
1. Document usage of bugzilla flags (suggested by jkeating) to track
blocker requests. This likely involves creating a ''bot'' to police the
tags?
2. Hardening the current keyword-based mechanism.
Additional discussion points include:
1. Document generating exception report and document action plan for
CLOSED Blocker bugs that did not go through VERIFIED.
2. More frequent nag mails leading up to release milestones. Notification
of NEW or ASSIGNED bugs goes to the maintainer, and MODIFIED bugs goes to
QA.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/89>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #149: Mentor Request
by fedora-badges
#149: Mentor Request
-----------------------------------------+----------------------------------
Reporter: hellork | Owner:
Type: proventester request | Status: new
Priority: minor | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
= phenomenon =
I am interested in joining the protesters and I'm requesting a mentor.
= reason =
I have been filing bug reports and working on submitting a couple new
projects to Fedora. I have a good working knowledge of Yum update, C, C++,
Makefiles, Bash, Python, Java, and RPM, packaging, etc.
= recommendation =
Sign me up!
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/149>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #196: proventester request
by fedora-badges
#196: proventester request
-----------------------------------------+----------------------------------
Reporter: azur3l1ght | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Hi , i would like to apply for proven testers team. I have 4 years as QA
in different projects and recently switched to Fedora .
Greetings
Georgi
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/196>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months