Show pageHistoryMedia Last modified: 2016/04/17 11:33 by flocculant

Sitemap

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

Both sides previous revisionPrevious revision
Next revision		Previous revision
qa:isotesting [2016/04/17 11:33] – flocculantqa:isotesting [2018/05/10 19:35] (current) – flocculant
Line 1: Line 1:
 ===== ISO Testing ===== ===== ISO Testing =====
  
-==== Milestones ====+==== ISO Test Builds ====
  
-While Daily testing is an on-going requirement, at times during a development cycle we approach //Milestones//. At those points the iso build is halted in order that a period of prolonged testing can take place.  +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.
- +
-**NOTE:**  A milestone release goes out of date rapidly, they should only be used for testing when Xubuntu QA calls for it. +
- +
-^ Release  ^ Notes ^ +
-|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| | +
- +
-Dates for milestones can be found on the current Release Schedule.  +
- +
-Milestones, including Daily, are listed on the iso tracker, you will be able to see which are currently being tested. +
- +
-{{milestones.png}} +
- +
-==== Test Builds ==== +
- +
-Once you've visited the tracker and can see what builds are available for testing, you can now decide which of the available iso's you will test.+
  
 This page will look similar to this This page will look similar to this
Line 31: Line 11:
 After you have selected an architecture, you will see links at the top, select the Download information link After you have selected an architecture, you will see links at the top, select the Download information link
  
-{images.png}}+{{images.png}}
  
-You will now see all the download possibilities +You will now see all the download possibilities available to you, choose which suits you and download your iso for testing.
  
 {{downloads.png}} {{downloads.png}}
  
-If you are going to be regularly testing the iso <sup>1</sup>, 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. +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. This can make some difference in the amount to download, particularly useful if your speed is slow, spotty or you have download limits.
Line 57: Line 37:
 ==== Submitting Results ==== ==== Submitting Results ====
  
-Once you have moved through 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 +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}} {{reporting.png}}
Line 63: Line 43:
 If you have noted bugs during the testcase you have 2 options:  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.+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. 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.
  
Line 69: Line 50:
  
 ==== Notes ==== ==== Notes ====
-<sup>1</sup> If downloading the iso daily then it makes sense to use the link to the current iso, this being the latest iso at any point, perhaps in conjunction with an alias. For example one member of the QA team uses this 'image' alias to grab the daily for both the 32 and 64 bit iso's and to remove the zsync old file once done, changing the release name once a cycle, wily to xenial for instance:  
  
-alias image='cd /mnt/Spare/iso/Xubuntu/Xenial/ && zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/xenial-desktop-i386.iso.zsync && zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/xenial-desktop-amd64.iso.zsync && rm /mnt/Spare/iso/Xubuntu/Xenial/*.zs-old'+<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.