Error loading plugin include
ParseError: syntax error, unexpected 'include' (T_INCLUDE), expecting identifier (T_STRING) or '{'
More info is available in the error log.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

--- qa:isotesting [2016/04/10 11:40] – created flocculant
+++ qa:isotesting [2018/05/10 19:35] (current) – flocculant
@@ Line 1: / Line 1: @@
 ===== ISO Testing =====
-==== Milestones ====
+==== ISO Test Builds ====
-^ Release  ^ Notes ^
+Test builds available for testing are listed on the ISO [[http://iso.qa.ubuntu.com/ | tracker]], you can decide which of the available iso's you will test.
-|Alpha 1 (opt-in)| |
-|Alpha 2 (opt-in)| |
-|Beta 1 (opt-in)|Follows Feature Freeze/Debian Import Freeze |
-|Beta 2 |Follows UI and Documentation Freeze |
-|Release Candidate |Week prior to Release |
-|Final Release| |
-==== Test Builds ====
+This page will look similar to this
+{{builds.png}}
+After you have selected an architecture, you will see links at the top, select the Download information link
+{{images.png}}
+You will now see all the download possibilities available to you, choose which suits you and download your iso for testing.
+{{downloads.png}}
+If you are going to be regularly testing the iso, you might look at using [[https://help.ubuntu.com/community/ZsyncCdImage |Zsync]] to only download differences between your local copy and the released daily image.
+This can make some difference in the amount to download, particularly useful if your speed is slow, spotty or you have download limits.
+{{zsync.png}}
 ==== Test Instructions ====
+Once you have your iso, you can burn this to media or use a virtual machine to boot the iso. Once you are in a position to boot the iso, you will want to choose which testcase to run
+{{testcases.png}}
+Selecting one of the testcases will show you a page with some links at the top, followed by the testcase to follow
+{{links.png}}
+Follow the testcase text to the end, noting issues that you have seen.
 ==== Submitting Results ====
+Once you have completed the testcase you are in a position to report your result on the tracker, you will see this section of the tracker page directly following the testcase detail
+{{reporting.png}}
+If you have noted bugs during the testcase you have 2 options:
+Critical bugs: These are bugs which cause you to not pass the testcase. For example - you start the installer but are unable to complete. Mark your test as Failed.<sup>1</sup>
+Bugs: These are bugs discovered during the test, which don't affect the testcase. For example, an application not part of the test, crashes and you see the crash dialogue.
+Below the Submit button, you will see a list of bugs that other reporters have noted during the //same test and milestone// - regardless of when, a bug in a daily test could have been reported at the cycle start.
+==== Notes ====
+<sup>1</sup> You might find that your result gets edited, while there could be many reasons for this, it's possible that Xubuntu QA have un-failed your result, sometimes there is a fine line between a fail and pass and we might allow an issue under particular circumstances.