Show pageHistoryMedia Last modified: 2018/05/10 19:35 by flocculant

Sitemap

Differences

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

Link to this comparison view

Next revision		Previous revision
Last revisionBoth sides next revision
qa:isotesting [2016/04/10 11:40] – created flocculantqa:isotesting [2018/04/29 20:12] – no real changes, this is just a test knome
Line 2: Line 2:
  
 ==== Milestones ==== ==== Milestones ====
 +Not all testing cycles will use all the milestones available to us, though in general an LTS cycle will include them.
 +
 +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. 
 +
 +**NOTE:**  A milestone release goes out of date rapidly, they should only be used for testing when Xubuntu QA calls for it.
  
 ^ Release  ^ Notes ^ ^ Release  ^ Notes ^
Line 11: Line 16:
 |Final Release| | |Final Release| |
  
-==== Test Builds ====+Dates for milestones can be found on the current Release Schedule. 
 + 
 +Milestones, including Daily, are listed on the [[http://iso.qa.ubuntu.com/ |iso tracker]], you will be able to see which are currently being tested. 
 + 
 +{{milestones.png}} 
 + 
 +==== ISO 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 
 + 
 +{{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<sup>1</sup>.  
 + 
 +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 ==== ==== 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 ==== ==== 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>2</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> 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. Change the release name once a cycle, wily to xenial to suit, use your own path to the saved iso(s): 
 +
 +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>2</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.