5:12 p.m.
During the meeting today it was decided to combine the Proven Tester and Join Proven
Tester documentation. I haven't changed much:
The Proven Testers are a dedicated group of the [[QA|Fedora Quality Assurance]] Community
who work towards making sure packages in the [[Critical_Path_Packages|Critical Path]] are
not broken in [[Releases/Branched|Fedora Branched]] as well as [[Releases|Fedora Stable]].
They retrieve their updates from the [[updates-testing]] repository and report their
findings as karma using [[Bodhi]]. Positive karma from a proven tester is required for
each critical path update before it can be pushed to the stable repository.
A proven tester is a member of the
[https://admin.fedoraproject.org/accounts/group/view/proventesters proventesters] group.
Individuals who wish to join this group must first be mentored and approved.
== Testing Updates ==Proven testers verify a basic level of stability before releasing an
update to the public. They do not need to test for total correctness or ensure complete
test coverage. Some tests will vary depending on the type of the package, while others
must pass for all updates. Generally speaking, an update should successfully execute all
applicable [[critical path action]]s. The [[Fedora release criteria]] is another useful
guide for minimum testing criteria.
Proven testers verify updates by installing them from the updates-testing repository. To
ensure rapid detection of regressions, a full system update from this repository should be
performed at least once a day. Individual packages may be updated more quickly if the need
for verification is urgent.
=== General Tests ===# The system must be able to shut down and reboot.# The user must be
able to log in to the desktop.# The user must be able to access the network.
=== Testing Applications ===If the package is an application, run the application and
check that basic operations work.
=== Testing Libraries and Shared Components ===If it is a library or other shared
component, run an application which uses the component and ensure that that works.
== Feedback Procedures ==Since a proven tester's karma determines whether an update is
allowed to be promoted, they follow special procedures based on the severity of
regressions they encounter. Use {{package|fedora-easy-karma}} to list all installed
packages from the updates-testing repository and allow to file feedback on each one at a
time. Pay particular attention to updates whose description notes that they are critical
path updates.
=== Major bugs ===If you identified any serious problems in earlier testing and were able
to identify the package responsible, post negative feedback for that package. If possible,
please file a bug report on the problem and link to the bug report in your feedback
message. A good feedback message quickly and clearly identifies the behavior change and
the cause, if you were able to determine it.
=== Minor bugs ===If you identify a problem which is minor in nature and does not impede
the actual critical path functionality, please do not post negative feedback. Post neutral
or positive feedback with a note of the issue encountered (and a link to a bug report if
appropriate).
=== Previously reported bugs ===If your testing uncovers no problems but you see that
another tester has identified a serious problem with the package, please try to replicate
their problem, and post negative feedback if you are now able to confirm it. If you are
not able to confirm the problem but you suspect this may be because you cannot recreate
the necessary conditions, please post neutral feedback noting that you were unable to
duplicate the problem. Only post positive feedback if you are sure your testing indicates
the other reporter's negative feedback is a mistake.
=== Unfamiliar packages ===If you are not sure what the component does or how to test it,
do not post positive or negative feedback. If the above general tests of booting, network
functionality and update functionality identified no problems, it is fine to leave a
neutral feedback message noting that you were able to boot the system and perform critical
path tasks with the update installed.
== How to Join ==
The following steps are imperative to join the QA Proven Testers:
{||- style="color: white; background-color: #3074c2; font-weight: bold"
align="aligned"
|'''Step'''||'''Task'''||'''Details'''|-|1
|| Sign up for the [https://admin.fedoraproject.org/accounts/login Fedora Account System].
|| You must have a FAS account before you participate here.|-|2 || Pick a Mentor!|| As the
interested QA Community member, it is your responsibility to request a mentor from the
[https://fedorahosted.org/fedora-qa/ Fedora QA Trac] instance by filing a new ticket. |-|3
|| Apply for Proven Testers|| Details of the procedure to apply for the Proven Testers QA
group are below.|-
|}
Once these steps are complete and your mentor confirms you have demonstrated an
understanding of QA process and community, your application for approval to the Critical
Path Wranglers (Proven Testers) will be brought up for review with the current Critical
Path Wranglers (Proven Testers). Once approved by the Critical Path Wranglers, you will be
able to apply for, and be approved for, the
[https://admin.fedoraproject.org/accounts/group/view/proventesters ProvenTesters group]
within [https://admin.fedoraproject.org/accounts FAS.]
The [https://admin.fedoraproject.org/accounts/group/view/proventesters ProvenTesters
group] within [https://admin.fedoraproject.org/accounts FAS] will grant the ability to add
what is known as "weighted" karma inside of
[https://admin.fedoraproject.org/updates Bodhi] to the [[Critical_Path_Packages|Critical
Path]] packages within Fedora [http://fedoraproject.org/wiki/Releases/Branched Fedora
Branched]. Karma that is "weighted" is known as such because each package that
requires it must have, at minimum, a quota of weighted karma in addition to karma added by
all other QA Community members. This means that everyone can offer up karma to the
packages within [[Critical_Path_Packages|Critical Path]] but a certain number of Proven
Testers karma is required for that package to be approved as stable.
== Proven Testers Mentor Candidates ==A Mentor candidate is any current Proven Tester. An
interested QA Community Member who would like to become sponsored may request a current
Proven Tester as their Mentor as part of their trac ticket if they have a preference of
who mentors them. Once the candidate Mentor accepts the interested QA Community
Member's request this Mentor will oversee the interested member and help them work
within the Critical Path QA efforts, policies, and procedures.
== External Links ==* [http://bodhi.fedoraproject.org Bodhi]* [http://redhat.bugzilla.com
Bugzilla]
<all>John Henry DulaneyVolunteer and Docent, North Carolina Maritime Museum
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&oci...