| 1 |
1 |
<?xml version="1.0" encoding="UTF-8"?> |
| 2 |
2 |
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" |
| 3 |
3 |
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ |
| 4 |
|
<!ENTITY % xubuntu-common SYSTEM "../ |
|
4 |
<!ENTITY % xubuntu-common SYSTEM "../../libs-common/xubuntu-common.ent"> |
| 5 |
5 |
%xubuntu-common; |
| 6 |
|
<!ENTITY % xubuntu-contributor-docs SYSTEM "../libs/xubuntu-contributor-docs.ent"> |
| 7 |
|
%xubuntu-contributor-docs; |
| 8 |
|
<!ENTITY % xinclude SYSTEM "../libs-common/xinclude.mod"> |
|
6 |
<!ENTITY % xubuntu-contributor SYSTEM "../libs/xubuntu-contributor.ent"> |
|
7 |
%xubuntu-contributor; |
|
8 |
<!ENTITY % xinclude SYSTEM "../../libs-common/xinclude.mod"> |
| 9 |
9 |
%xinclude; |
| 10 |
10 |
<!ENTITY language "&EnglishAmerican;"> |
| 11 |
11 |
<!ENTITY language "C"> |
| 12 |
12 |
]> |
| 13 |
13 |
|
| 14 |
14 |
<chapter id="qa-team"> |
| 15 |
|
<title>Xubuntu QA Team</title> |
|
15 |
<title>QA Team</title> |
| 16 |
16 |
|
| 17 |
17 |
<section id="qa-team-links"> |
| 18 |
|
<title>Useful links for the QA Team:</title> |
|
18 |
<title>Useful Links</title> |
|
19 |
|
| 19 |
20 |
<itemizedlist> |
| 20 |
21 |
<listitem><para><ulink url="https://trello.com/b/IV66JCHl/xubuntu-qa">Xubuntu QA Trello</ulink></para></listitem> |
| 21 |
22 |
<listitem><para><ulink url="https://launchpad.net/~xubuntu-qa">Xubuntu QA</ulink></para></listitem> |
| 22 |
23 |
<listitem><para><ulink url="https://launchpad.net/~xubuntu-testers">Xubuntu Testers</ulink></para></listitem> |
| 23 |
24 |
<listitem><para><ulink url="http://iso.qa.ubuntu.com/qatracker">ISO Tracker</ulink></para></listitem> |
| 24 |
25 |
<listitem><para><ulink url="http://packages.qa.ubuntu.com/">Package Tracker</ulink></para></listitem> |
| 25 |
|
<listitem><para><ulink url="https://wiki.ubuntu.com/QATeam">Ubuntu QA wiki</ulink></para></listitem> |
| 26 |
|
<listitem><para><ulink url="https://launchpad.net/ubuntu-manual-tests/">Ubuntu Manual Test Project</ulink></para></listitem> |
|
26 |
<listitem><para><ulink url="https://wiki.ubuntu.com/QATeam">Ubuntu QA Team Wiki</ulink></para></listitem> |
|
27 |
<listitem><para><ulink url="https://launchpad.net/ubuntu-manual-tests/">Ubuntu Manual Tests</ulink></para></listitem> |
| 27 |
28 |
</itemizedlist> |
| 28 |
29 |
</section> |
| 29 |
30 |
|
| 30 |
31 |
<section id="qa-team-basics"> |
| 31 |
|
<title>Xubuntu QA Team</title> |
| 32 |
|
<para> The Xubuntu QA team was formed to ensure that the quality of a released Xubuntu conforms to the parameters laid out in the Xubuntu Processes documents. In order to successfully accomplish this, close team working relationships, especially with the Development team and the Project Lead are paramount. Xubuntu's success is based on close working amongst all of it's various teams.</para> |
|
32 |
<title>QA Team</title> |
|
33 |
|
|
34 |
<para>The Xubuntu QA team was formed to ensure that the quality of a released Xubuntu conforms to the parameters laid out in the Xubuntu Processes documents. In order to successfully accomplish this, close team working relationships, especially with the Development team and the Project Lead are paramount. Xubuntu's success is based on close working amongst all of its various teams.</para> |
| 33 |
35 |
|
| 34 |
|
<para>In addition, the team gives people contributing through testing of Xubuntu the opportunity to become part of the <ulink url="https://launchpad.net/~xubuntu-team">Xubuntu Team</ulink> through their contributions. For that to be of practical use, the QA team should keep watch on testing reports on the tracker(s) and propose users they have seen taking a keen interest in the work of the QA Team.</para> |
|
36 |
<para>In addition, the team gives people contributing through testing of Xubuntu the opportunity to become part of the <ulink url="https://launchpad.net/~xubuntu-team">Xubuntu Team</ulink>. For that to be of practical use, the QA team should keep an eye on testing reports on the trackers and propose users they have seen taking a keen interest in the work of the QA team.</para> |
| 35 |
37 |
|
| 36 |
38 |
<para>Excluding testing itself, control of the testcases that we use for ISO and Package testing, along with communicating the testing requirements for any particular development cycle (hereafter cycle) to the community, makes up the bulk of the teams work in any given cycle.</para> |
| 37 |
39 |
|
| … |
| 42 |
43 |
<section id="qa-team-testing"> |
| 43 |
44 |
<title>Testing Responsibilities</title> |
| 44 |
45 |
|
| 45 |
|
<para>At the start of a cycle, the Release Team will discuss which ISO Milestones we will participate in. Then, during a Community Meeting, members of Xubuntu Team will discuss and then ratify Xubuntu's participation during the cycle. </para> |
|
46 |
<para>At the start of a cycle, the Release Team will discuss which ISO Milestones we will participate in. Then, during a Community Meeting, members of Xubuntu Team will discuss and then ratify Xubuntu's participation during the cycle.</para> |
| 46 |
47 |
|
| 47 |
|
<para>Along with general testing of our OS, dealt with further in <xref linkend="qa-testing-exploratory"/> and <xref linkend="qa-testing-ppa"/>, further responibilities lie with ensuring that: |
|
48 |
<para>Along with general testing of our OS, dealt with further in <xref linkend="qa-testing-exploratory" /> and <xref linkend="qa-testing-ppa" />, further responsibilities lie with ensuring that:</para> |
| 48 |
49 |
|
| 49 |
50 |
<itemizedlist> |
| 50 |
|
<listitem><para>Sufficient testing takes place prior to ISO milestone release</para></listitem> |
| 51 |
|
<listitem><para>Sufficient Package testing takes place following calls to testers</para></listitem> |
|
51 |
<listitem><para>Sufficient testing takes place prior to ISO Milestone releases</para></listitem> |
|
52 |
<listitem><para>Sufficient package testing takes place following calls to testers</para></listitem> |
| 52 |
53 |
<listitem><para>Sufficient testing has taken place by Final Release</para></listitem> |
| 53 |
54 |
<listitem><para>Bugs reported to our trackers are confirmed, or where unable to confirm, further information is requested from the reporter</para></listitem> |
| 54 |
55 |
<listitem><para>Where appropriate, confirmation of bugs can be asked of members of Xubuntu Team in the team devel IRC channel</para></listitem> |
| 55 |
56 |
</itemizedlist> |
| 56 |
|
</para> |
| 57 |
|
|
| 58 |
|
<para>Members of the QA team might find it useful subscribing to the <ulink url="https://launchpad.net/~xubuntu-bugs">Xubuntu Bugs Team</ulink> in order to be aware of bugs being reported by users.</para> |
| 59 |
57 |
|
|
58 |
<para>Members of the QA team might find it useful subscribing to the <ulink url="https://launchpad.net/~xubuntu-bugs">Xubuntu Bugs</ulink> team in order to be aware of bugs being reported by users.</para> |
| 60 |
59 |
</section> |
| 61 |
60 |
|
| 62 |
61 |
<section id="qa-team-trackers"> |
| 63 |
62 |
<title>Working with the QA Trackers</title> |
| 64 |
63 |
|
| 65 |
|
<para>The initial decision(s) on what and when to test, will be taken following discussion with the members of the <ulink url="https://launchpad.net/~xubuntu-release">Xubuntu Release Team</ulink></para>. |
|
64 |
<para>The initial decisions on what and when to test, will be taken following discussion with the members of the <ulink url="https://launchpad.net/~xubuntu-release">Xubuntu Release</ulink> team.</para> |
| 66 |
65 |
|
| 67 |
|
<para>At the start of a cycle, the QA team needs to ensure that: |
|
66 |
<para>At the start of a cycle, the QA team needs to ensure that:</para> |
| 68 |
67 |
|
| 69 |
68 |
<itemizedlist> |
| 70 |
69 |
<listitem><para>Image testcases we use are still correct.</para></listitem> |
| 71 |
70 |
<listitem><para>When the intention is that package testing will take place during the cycle, package testcases are still correct.</para></listitem> |
| 72 |
|
<listitem><para>The testsuites on the Package Tracker make sense for what we intend to test during the cycle. Differences between regular and LTS releases are often, but not always, needed</para></listitem> |
| 73 |
|
<listitem><para>Scheduling of ISO, and when appropriate Package, Testing should take place amongst the QA Team. The resulting schedule should be posted on the Xubuntu QA Trello page with Due Dates, this ensures that the schedule shows on the tracker's calendar tab.</para></listitem> |
|
71 |
<listitem><para>The testsuites on the Package Tracker make sense for what we intend to test during the cycle. Differences between regular and LTS releases are often, but not always, needed.</para></listitem> |
|
72 |
<listitem><para>Scheduling of ISO, and when appropriate Package, testing should take place amongst the QA team. The resulting schedule should be posted on the Xubuntu QA Trello page with Due Dates, this ensures that the schedule shows on the tracker's calendar tab.</para></listitem> |
| 74 |
73 |
</itemizedlist> |
| 75 |
|
</para> |
| 76 |
74 |
|
| 77 |
75 |
<para>When there are changes to a package we test, following for example a bug fix, a further check of the testcase involved should take place. Further testing calls for that package should be made to check for regression during the cycle.</para> |
| 78 |
76 |
|
| … |
| 79 |
77 |
<para>When a package during test constantly fails, or bug reports indicate a failure in a package for something not tested. The testcase for that package should be disabled temporarily. This should be noted on the Trello Disabled Tests list. The QA Lead is responsible for ensuring tests are both disabled and re-enabled when appropriate.</para> |
| 80 |
78 |
</section> |
| 81 |
79 |
|
| 82 |
|
|
| 83 |
80 |
<section id="qa-team-testedits"> |
| 84 |
|
<title>Working with testcases</title> |
|
81 |
<title>Working with Testcases</title> |
| 85 |
82 |
|
| 86 |
83 |
<para>Information on the basic method of working with testcases can be found at the Ubuntu QA Team <ulink url="https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual">Manual Testcases</ulink> page.</para> |
| 87 |
84 |
|
| 88 |
85 |
<para><emphasis>We</emphasis> are only concerned with a specific set of tasks: grabbing the branch, making edits and then pushing the changes we need to the main branch. We have people in the Testcase Admin team for the LP Testcases, in addition any member of our Release Team can edit the tracker, this helps ensure that changes are moved through to the trackers quickly.</para> |
| 89 |
86 |
|
| 90 |
|
<para>To edit a testcase: |
|
87 |
<para>To edit a testcase:</para> |
| 91 |
88 |
|
| 92 |
89 |
<itemizedlist> |
| 93 |
|
<listitem><para>Report the required change as a bug report to the <ulink url="https://bugs.launchpad.net/ubuntu-manual-tests/+filebug">testcase project</ulink></para></listitem> |
|
90 |
<listitem><para><ulink url="https://bugs.launchpad.net/ubuntu-manual-tests/+filebug">Report</ulink> the required change as a bug against the testcase project</para></listitem> |
| 94 |
91 |
<listitem><para>Assign yourself to the bug</para></listitem> |
| 95 |
|
<listitem><para><userinput>bzr branch lp:ubuntu-manual-tests</userinput></para></listitem> |
| 96 |
|
<listitem><para>Make changes to the testcase(s)</para></listitem> |
| 97 |
|
<listitem><para>Commit the change with <userinput>bzr commit -m "Change re bug#</userinput>, make bug # reflect the bug you reported above</para></listitem> |
| 98 |
|
<listitem><para>Push the change to your branch <userinput>bzr push lp:~yourusername/ubuntu-manual-tests/#</userinput>.</para></listitem> |
|
92 |
<listitem><para>Create a local branch: <userinput>bzr branch lp:ubuntu-manual-tests</userinput></para></listitem> |
|
93 |
<listitem><para>Make changes to the testcase in your local branch</para></listitem> |
|
94 |
<listitem><para>Commit the changes: <userinput>bzr commit --fixes lp:# -m "Fix bug #</userinput> - make <literal>#</literal> reflect the bug you reported above</para></listitem> |
|
95 |
<listitem><para>Push the changes to a personal repository: <userinput>bzr push lp:~yourusername/ubuntu-manual-tests/bug-#</userinput></para></listitem> |
| 99 |
96 |
</itemizedlist> |
| 100 |
|
</para> |
| 101 |
97 |
|
| 102 |
|
<para>Once pushed to your local branch, propose the change for merging - <xref linkend="bzr-merge-proposal" /></para> |
|
98 |
<para>Once pushed to a personal repository, propose the change for merging - <xref linkend="bzr-merge-proposal" />.</para> |
|
99 |
|
| 103 |
100 |
<para>Respond to any requests for changes when asked by the Testcase Admins in order to get the required change through in a timely manner.</para> |
| 104 |
101 |
</section> |
| 105 |
102 |
|
| 106 |
103 |
<section id="qa-team-users"> |
| 107 |
104 |
<title>Communicating with Testers and Users</title> |
| 108 |
105 |
|
| 109 |
|
<para>While we have 2 sets of people in the community that we contact about required testing. Testers will get regular contact from us, we should only, in general, call on Users at later stages.</para> |
|
106 |
<para>While we have two sets of people in the community that we contact about required testing, Testers will get regular contact from us, but we should only, in general, call on Users at later stages.</para> |
| 110 |
107 |
|
| 111 |
|
<para>The team lead will be an administrator on the Testers Launchpad page and can contact those users via LP. Copies of testing calls sent to the dev mailing list should go to this group each time</para> |
|
108 |
<para>The QA Lead will be an administrator on the Testers Launchpad page and can contact those users via LP. Copies of testing calls sent to the devel mailing list should go to this group each time.</para> |
| 112 |
109 |
|
| 113 |
|
<para>Any member of the QA team can: |
|
110 |
<para>Any member of the QA team can:</para> |
| 114 |
111 |
|
| 115 |
112 |
<itemizedlist> |
| 116 |
|
<listitem><para>Watch dates on the Trello schedule for upcoming test calls via the tracker's calendar <ulink url="http://tracker.xubuntu.org/#tab-calendar">page</ulink></para></listitem> |
| 117 |
|
<listitem><para>Mail the -dev list with a testing call</para></listitem> |
| 118 |
|
<listitem><para>Prior to ISO Milestones, mail the -dev list just prior to a testdate warning testers of upcoming ISO calls</para></listitem> |
| 119 |
|
<listitem><para>Make ISO Milestone testing calls</para></listitem> |
|
113 |
<listitem><para>Watch dates on the Trello schedule for upcoming testing calls via the tracker's <ulink url="http://tracker.xubuntu.org/#tab-calendar">calendar</ulink> tab</para></listitem> |
|
114 |
<listitem><para>Mail the devel list with a testing call</para></listitem> |
|
115 |
<listitem><para>Just prior to an upcoming ISO Milestone testing call, warn on the devel list</para></listitem> |
|
116 |
<listitem><para>Make an ISO Milestone testing call</para></listitem> |
| 120 |
117 |
</itemizedlist> |
| 121 |
|
</para> |
| 122 |
|
|
| 123 |
|
<para>Xubuntu Users will be contacted for ISO testing at later ISO Milestones, at the earliest the Beta 1 milestone, depending on the state of the current ISO and our packages</para> |
| 124 |
118 |
|
|
119 |
<para>Xubuntu Users will be contacted for ISO testing at later ISO Milestones, at the earliest the Beta 1 milestone, depending on the state of the current ISO and our packages.</para> |
| 125 |
120 |
</section> |
| 126 |
121 |
|
| 127 |
122 |
<section id="qa-team-release"> |
| 128 |
123 |
<title>Release Responsibilities</title> |
| 129 |
124 |
|
| 130 |
|
<para>Much of the responsibility for the QA team at any release lies with the QA Lead |
|
125 |
<para>Much of the responsibility for the QA team at any release lies with the QA Lead.</para> |
|
126 |
|
|
127 |
<para>However, <emphasis>any</emphasis> member of the QA team can:</para> |
| 131 |
128 |
|
| 132 |
|
<para>However, <emphasis>any</emphasis> member of the QA team can : |
| 133 |
129 |
<itemizedlist> |
| 134 |
130 |
<listitem><para>Work with the draft wiki <ulink url="https://wiki.ubuntu.com/Xubuntu/Testing/ReleaseNoteBase">Release Note</ulink></para></listitem> |
| 135 |
|
<listitem><para>Check status of bugs listed on draft</para></listitem> |
| 136 |
|
<listitem><para>Check status of work items on the QA Launchpad blueprints, marking as appropriate.</para></listitem> |
|
131 |
<listitem><para>Check status of bugs listed on the above draft</para></listitem> |
|
132 |
<listitem><para>Check status of work items on the QA blueprint, marking as appropriate</para></listitem> |
| 137 |
133 |
</itemizedlist> |
| 138 |
|
</para> |
| 139 |
|
|
| 140 |
134 |
</section> |
| 141 |
135 |
|
| 142 |
136 |
<section id="qa-post-release"> |
| … |
| 145 |
139 |
<para>Following release, there are a few tasks that need to be done before the next release cycle begins.</para> |
| 146 |
140 |
|
| 147 |
141 |
<itemizedlist> |
| 148 |
|
<listitem><para>QA Team Lead should set up the pages for both the QA Team and the Bug blueprints the whole team uses.</para></listitem> |
| 149 |
|
<listitem><para>Any member of the QA Team can archive the previous cycle Testing , Postponed and Done card(s)</para></listitem> |
|
142 |
<listitem><para>QA Lead should set up the blueprints for both the QA team and the Bugs that the whole team uses</para></listitem> |
|
143 |
<listitem><para>Any member of the QA team can archive the previous cycle's Testing, Postponed and Done cards</para></listitem> |
| 150 |
144 |
<listitem><para>Set up new cycle cards for Testing, Postponed and Done</para></listitem> |
| 151 |
145 |
<listitem><para>Check that notes in the Tester Notes card is up to date</para></listitem> |
| 152 |
|
<listitem><para>Check that the Draft Release Note is up to date</para></listitem> |
|
146 |
<listitem><para>Check that the draft Release Note is up to date</para></listitem> |
| 153 |
147 |
</itemizedlist> |
| 154 |
|
|
| 155 |
148 |
</section> |
| 156 |
149 |
</chapter> |
