<JoseeAntonioR> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/13/%23ubuntu-classroom.html following the conclusion of the session.
<smartboyhw> JoseeAntonioR, thanks!
<JoseeAntonioR> :)
<smartboyhw> Hello everyone!
<smartboyhw> I'm Howard Chan, an active QA contributor mainly doing ISO testing.
* ChanServ quita voz a balloons
* ChanServ da voz a balloons2
<smartboyhw> If you have been paying attention to our previous sessions, you would have learnt:
<smartboyhw> How to sign up in Launchpad and mailing list
* jackyalcine es ahora conocido como zz_jackyalcine
<smartboyhw> How to use the wiki and IRC and toolset
* zz_jackyalcine es ahora conocido como jackyalcine
<smartboyhw> How to write manual testcases and report bugs
<smartboyhw> How to use zsync, VirtualBox, KVM and testdrive
<smartboyhw> And finally, how to do laptop testing
<smartboyhw> So today we are doing ISO testing!
<smartboyhw> Why do we need to do ISO testing?
<smartboyhw> When a normal user goes and installs Ubuntu, there are many ways that he/she will install Ubuntu
<smartboyhw> For example, using a desktop image
<smartboyhw> Or using Wubi
<smartboyhw> Even maybe a netboot ISO
<smartboyhw> If a user meets a bug during installation, he will get unpleased or maybe even remove Ubuntu, which we absolutely don't want to
<smartboyhw> mote asked: ISO testing are mainly to test the installation process?
<smartboyhw> Well mote: You are correct!
<smartboyhw> We normally do ISO testing to make sure they are bug-free (at least critical-bug-free) and that they can install it
<smartboyhw> That's one of the main testing roles we do
<smartboyhw> So what do you need ?
<smartboyhw> 1. A Launchpad account. It shouldn't be difficult if you have been following balloons2's sessions
<smartboyhw> *session
<JoseeAntonioR> mote asked:  Are testing in WM, not insuffient, as many problems are due to hardware setup?
<smartboyhw> mote, I can't really understand the question.....
<smartboyhw> But if mote is asking about VMs are not good enough
<smartboyhw> Then yes!
* jackyalcine es ahora conocido como zz_jackyalcine
* zz_jackyalcine es ahora conocido como jackyalcine
<smartboyhw> For example, if we want to test UEFI bootloaders it would be difficult to do so in a VM.
<smartboyhw> So this is our second requirement for doing ISO tests: A real machine (spare one, don't use your main one) or a VM
<smartboyhw> You can have multiple choices
<smartboyhw> For example Oracle VM VirtualBox, VMware Player, Testdrive or KVm
<JoseeAntonioR> nearst asked: can we use this iso test for example when i backup my ubuntu with remastersys?
<smartboyhw> nearst, the ISO test must go through an ISO (image) installation
<smartboyhw> So if the backup is just simply an backup then no
* smartboyhw has never used remastersys before
<JoseeAntonioR> plustwo asked: if using a VM for ISO testing, would the results be close enough to testing using physical h/w?
<smartboyhw> plustwo: Nice one
<smartboyhw> Answer: Not quite
<smartboyhw> As I have said before, it can be completely different
<smartboyhw> For example, you can't really do wireless connection in  a VM
<smartboyhw> But when you can't connect to the network in a real machine using wireless, that is a problem
<JoseeAntonioR> GridCube asked: Which tests are critical on alpha, beta, and final release tests?
<smartboyhw> GridCube, basically everything
<smartboyhw> We need to make sure all the tests can pass on release
<smartboyhw> GridCube, for example
<smartboyhw> Kubuntu can't release their 13.04 Alpha 1 amd64+mac images
<smartboyhw> Since the tests aren't met
<smartboyhw> Especially when final release all tests must be a passed one
* jackyalcine es ahora conocido como zz_jackyalcine
* zz_jackyalcine es ahora conocido como jackyalcine
<smartboyhw> In Alpha releases we normally use Virtual machines
<smartboyhw> In beta and especially in final releases though we use real machines to do testing
<smartboyhw> So, any questions about the requirements?
<smartboyhw> If not let's move on.
<smartboyhw> Now, if you have read the wiki page https://wiki.ubuntu.com/Testing/Activities/Classroom/Section3
<smartboyhw> (which is included in the classroom blog post
<smartboyhw> You should have downloaded an ISO.
<smartboyhw> I myself will test a Ubuntu 12.04.2 Desktop amd64 image today
<smartboyhw> Alongside you guys:)
<JoseeAntonioR> plustwo asked: can one select which part of the ISO testing to do and send the test results back to you guys?
<smartboyhw> plustwo, certainly!
<smartboyhw> That is exactly what I want to talk about later
<smartboyhw> The ISO tracker
<smartboyhw> But for the first part of the question: You can freely choose whatever flavour you want
<smartboyhw> For example, Ubuntu 12.04.2 Alternate amd64
<smartboyhw> Or Ubuntu Studio 12.04.2 DVD i386
<smartboyhw> Or Kubuntu Desktop 13.04 Alpha 2 amd64
<JoseeAntonioR> nearst asked: if im setup vmware with usb wireless connect to vm, is it pass for requirement?
<smartboyhw> nearst: Hmm
<smartboyhw> The problem is that even though you have done that
<smartboyhw> It still doesn't really emulate the real hardware environment
<smartboyhw> Sure that is also OK. It is just that it isn't good enough
<smartboyhw> Enough questions? We need to move on:P
<smartboyhw> Now if you haven't downloaded an ISO please download one at cdimage.ubuntu.com
<balloons2> it would help test the installer, and usb wireless may be used, but as smartboyhw said, if possible real hw is preferred. its very much a valid testpoint though and useful to have
<smartboyhw> That's the point of using real h/w
<smartboyhw> Of course if you want to test the same ISO as mine
<smartboyhw> Download it from http://cdimage.ubuntu.com/precise/daily-live/current
<balloons2> I actually think the usb wireless in a vm is kind of slick ;-)
* jackyalcine es ahora conocido como zz_jackyalcine
<smartboyhw> Yes 1
* zz_jackyalcine es ahora conocido como jackyalcine
<smartboyhw> * Yes !
<smartboyhw> Now let's drop in into the ISO QA Tracker!!!!
<smartboyhw> Go to iso.qa.ubuntu.com
<smartboyhw> You should see a "Log in" button on the left-hand side
<smartboyhw> Click on it, enter your Launchpad e-mail address and password
<smartboyhw> Then click "Log in again"
<smartboyhw> You should see a page about what credentials would you like to share
<smartboyhw> Just click "Yes, sign me in"
<smartboyhw> After login, you should see your launchpad nick on the top-right hand corner
<smartboyhw> Raring Alpha 2 and Precise 12.04.2 is going to be released tomorrow (seriously) so we need to set these images as priority
<smartboyhw> We shall ignore Raring Alpha 2 since only Kubuntu is going to have it, other flavours don't
<smartboyhw> So let
<smartboyhw> us click on "Precise 12.04.2"!
<smartboyhw> In this page you can see all the ISO images available for testing, the number of testcases done and also the number of bugs....
<smartboyhw> Since I downloaded a Ubuntu Desktop image, I shall select "Ubuntu Desktop amd64"
* balloons2 notes if you have a different iso downloaded you can still follow along without worry
<smartboyhw> Then you shall see the testcases available for you to test:)
<smartboyhw> If you don't want to follow me no worries
<smartboyhw> Plenty of ISOs for you to choose from (LOL)
<smartboyhw> Now I'm going to do "Install (entire disk)" since I'm going to use VirtualBox
<smartboyhw> To start with:)
<smartboyhw> Click on the testcase you want to help test
<smartboyhw> And in the testcase page click on testcase
<smartboyhw> You might wonder why there is only a link to testcases.qa.ubuntu.com instead of a full testcase listed here for convenience
<smartboyhw> Truth be told: It isn't available for Precise only
<smartboyhw> If you go click on the Raring testcases you shall see full beautifully-written testcases, written by the testcase admins team
<smartboyhw> phillw should have taught you how to write one:)
<smartboyhw> So now: It is time to start installing the image!
<smartboyhw> So first of all I'm setting up my VirtualBox VM
<smartboyhw> Launch VirtualBox (If you haven't installed it, type "sudo apt-get install virtualbox virtualbox-dkms"
<smartboyhw> Select "New"
<smartboyhw> Click "Next"
<smartboyhw> Type whatever the name you want (it doesn't matter)
<smartboyhw> For me I will be using this name:
<smartboyhw> "Ubuntu 12.04.2 LTS 20130211 64-bit"
<smartboyhw> Make sure in "OS Type" the Operating System is "Linux" and the version is "Ubuntu" or "Ubuntu (64 bit)"
<smartboyhw> Select a suitable memory size
<smartboyhw> You don't want too much (unless you have a machine with 1TB ram:P)
* jackyalcine es ahora conocido como zz_jackyalcine
<smartboyhw> Click "Next" (and sorry for missing it between the operating system and the memory part)
<smartboyhw> Tick "Start-up Disk" and choose "Create new hard disk"
<smartboyhw> Click "Next" again and the "virtual disk creation wizard" shall appear
<smartboyhw> For this test I will choose "VDI (VirtualBox Disk Image)
<smartboyhw> Click "Next"
<smartboyhw> You can either choose "dynamically allocated" or "fixed size".
<smartboyhw> However if you are planning to have a big Virtual disk use "dynamically allocated"
<smartboyhw> Click "Next"
<smartboyhw> Leave the file location by default
<smartboyhw> Select the disk size. Make sure it is at least 6 GB.
<smartboyhw> The default (8 GB) should be good enough anyway
<smartboyhw> Click "Next"
<smartboyhw> Make sure nothing is wrong, then select "Create"
<smartboyhw> Same screen again for the VM.
<smartboyhw> Click "create" and you have successfully created a VirtualBox VM!
<smartboyhw> Click "start" (don't worry about your ISO image not yet used, it is coming!)
<smartboyhw> You might have some messages popping out, so just click "OK" for these.
<smartboyhw> You shall see a "First run Wizard" if you hadn't chose an ISO image for the VM.
<smartboyhw> Click "next"
<smartboyhw> Select the ISO you downloaded
<smartboyhw> Click "Next" again
<smartboyhw> Click "start"
<smartboyhw> We are now booting the image!!!!!
<smartboyhw> Now listen: You might have problems using VirtualBox for this image because I delibrately selected one image that has a bug so you can see how to submit a failed result....
<smartboyhw> You should have a blank screen with a orange cursor
<smartboyhw> You might ask: Are you kidding me?
<smartboyhw> no
<smartboyhw> For those of you who are using other hardware, use these prodecures to test
<smartboyhw> Make sure you see a screen that has two buttons: "Try Ubuntu" and "Install Ubuntu"
<smartboyhw> Click on "Install Ubuntu"
<smartboyhw> Make sure all three requirements (or two) listed on the page are with a green tick!
<smartboyhw> You can choose whether to tick "Download updates while installing" and/or "Install this third-party software'
<smartboyhw> Click "Continue"
<smartboyhw> For "Installation type" click "Erase disk and Install Ubuntu"
<smartboyhw> Again click "continue"
<smartboyhw> Make sure that the full drive space is allocated, the drive space is correct and such.
<smartboyhw> Click on "Install now"!
<smartboyhw> You should then (if you have internet connection) put into a screen where your timezone is selected
<smartboyhw> Check that it is correct
<smartboyhw> If it is, click "Continue"
<smartboyhw> If it isn't, select the correct timezone and then continue
<smartboyhw> After that you should land on a "Keyboard Layout" page.
<smartboyhw> Select the correct Keyboard Layout, test it by typing into the test area, then click "Continue"
<smartboyhw> In the screen "Who are you?" you should input your real name, your computer name, your username, your password (twice) and select whether you want to login automatically or needing a password to log in
<smartboyhw> If you need a password to log in, you can also choose to encrypt your home partition
<smartboyhw> Then click "Continue"
<smartboyhw> The slides should be playing now and change automatically. Make sure you can navigate through slides via clicking on the arrows
<smartboyhw> Don't forget: If you have any question, use the QUESTION: tag to ask it in #ubuntu-classroom-chat !
<smartboyhw> The installation will take a while, so relax for a bit
<smartboyhw> If you have any bugs while installing, report them!
<smartboyhw> Press Ctrl+Alt+F1 to launch terminal
<smartboyhw> then type "apport-bug ubiquity" to report a bug against the installer
<smartboyhw> Actually
<smartboyhw> if you have problems with the ISO image, type "ubuntu-bug syslinux"
<JoseeAntonioR> GridCub asked: apport-bug its the same as ubuntu-bug?
<smartboyhw> GridCube, YES
<smartboyhw> apport-bug = ubuntu-bug
<smartboyhw> I used apport-bug more, but that's just your personal preference
<smartboyhw> If you have problems with graphics, use ubuntu-bug xorg
<smartboyhw> For VirtualBox users who can't install: Follow me!
<JoseeAntonioR> plustwo asked: if bugs are not reported like today and the release happens tomorrow, will the ISO tests results still be valid?
<smartboyhw> plustwo, frankly: Yes.
<smartboyhw> There would be no way to save the release
<smartboyhw> Also guys: The results you handed in might be invalid after the images went through a respin
<smartboyhw> VirtualBox users: At that page's "Results" box
<smartboyhw> Click on "failed"
<smartboyhw> In critical bugs type 1122072
<smartboyhw> Then click "Submit result"
<smartboyhw> Has anyone finished the test and it shows "Installation completed"?
<smartboyhw> If yes, click on "Restart now"
<smartboyhw> Remove the disk (if you used a real one), close the tray (if your CD driver is a tray) and press "Enter"
<smartboyhw> It should auto reboot
<smartboyhw> Login and that's it!
<smartboyhw> Don't hand in a pass result yet, instead, we need to do vertification
<smartboyhw> First of all, open a terminal, and type "arch"
<smartboyhw> It should show the correct architecture of the ISO you installed.
<smartboyhw> Then type "lsb_release -a"
<smartboyhw> The DIstributor ID should be Ubuntu
<smartboyhw> Description should be Ubuntu 12.04.2
<smartboyhw> Release should be 12.04
<smartboyhw> Codename should be precise
<smartboyhw> Then try "sudo apt-get update" and make sure it doesn't throw any errors.
<smartboyhw> Then you can really submit a pass result!
<smartboyhw> In the "results" block of the testcase page select "passed"
<smartboyhw> However if you got any bugs that you found during installation but doesn't block it, type the bug number in the "bugs" section
<JoseeAntonioR> GridCube asked: What if you finished a test, and it took a long time to complete, say you used a real hw which is slow, and you find a bug, but when you go to report it the iso was already rolled away for a different bug. can you still report the found bug against the new release?
<smartboyhw> GridCube, hmm. We need to test it again. However if that bug isn't related to the bug you found, it probably still exists
<smartboyhw> Make sure you test it again though.