[18:07] <speckmade> So the Ubuntu User Days will happen in here, I hear. Now what does "presentation" mean - will the presenters just flood us with chat messages or will there be a video stream or something?..
[18:08] <pleia2> they talk in here (I wouldn't call it a "flood" - it's normal chatting speed)
[18:09] <pleia2> then you ask questions and discuss what's going on in the session in #ubuntu-classroom-chat
[20:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/07/%23ubuntu-classroom.html following the conclusion of the session.
[20:01] <primes2h> Hello all and welcome to this intro on Ubuntu Laptop testing!
[20:02] <primes2h> This classroom session is going to be held by three members of the Laptop Testing Team: https://launchpad.net/~ubuntu-laptop-testing.
[20:02] <primes2h> This session goes to be hosted by Sergio Zanchetta (primes2h), Sergio Andres Meneses (SergioMeneses) and Carla Sella (Letozaf_)....
[20:03] <primes2h> So let’s first introduce ourselves:
[20:03] <primes2h> I’m Sergio Zanchetta from the Ubuntu Italian Team. My work in Ubuntu is mainly on translations and testing.
[20:03] <primes2h> I’m a member of the Ubuntu Italian Translators Team, Ubuntu QA Team, one of the founders of the Italian Testing Team and an administrator of the Laptop Testing Team, which I founded as well.
[20:04] <primes2h> Here you can find more information about me: https://launchpad.net/~primes2h.
[20:04] <SergioMeneses> hi all!
[20:04] <SergioMeneses> my name is Sergio Andres Meneses, I’m from Ubuntu Colombian Team, I actually work with the Ubuntu Loco Council and the Ubuntu QA team in the Laptop testing field from this cycle :)
[20:05] <SergioMeneses> you can find more information about me in my wiki page: https://wiki.ubuntu.com/SergioMeneses
[20:05] <letozaf> Hello to everyone
[20:05] <letozaf> My name is Carla Sella, I’m Italian and I’m member of the  Ubuntu QA Team,  Italian Testing Team and Laptop testing team.
[20:05] <letozaf> I have been testing for about a couple of years now and I am mostly involved in manual and automated testing, you can find information about me here: https://launchpad.net/~carla-sella.
[20:06] <SergioMeneses> Today we're going to learn about "Testing on a Laptop".
[20:07] <letozaf> You may ask questions at any point.. Just be sure to utilize the #ubuntu-classroom-chat channel So let's get started!
[20:07] <primes2h> Why do we test laptops?
[20:08] <primes2h> As you can see on the laptop testing wiki page: https://wiki.ubuntu.com/Testing/Laptop
[20:08] <primes2h> “We're on a mission to get Ubuntu to work great on as many different makes and models of laptops as possible.”
[20:08] <SergioMeneses> In fact the aim of the project is to find out all the bugs affecting laptops hardware during the development process, so that developers can fix them in time for the release.
[20:09] <primes2h> Besides, not less important, is to keep track of bugs themselves also after a stable image has been released.
[20:09] <letozaf> So anyone that has a laptop has the chance to test how Ubuntu works on it and in case they have nasty problems with some hardware they can report a bug and help get their problems solved.
[20:10] <letozaf> This way they will help make Ubuntu work on a larger number of laptops and hardware.
[20:10] <letozaf> Tests are carried out following  testcases that tell you how to  run tests on your laptop, each one is designed to find out if a specific piece of hardware works straight off. Any bugs have to be reported in launchpad and added in the Laptop Tracker.
[20:11] <primes2h> These tests are run in either stable releases or current milestone of development release.
[20:11] <SergioMeneses> We will now explain how to start your adventure in Laptop testing:
[20:11] <SergioMeneses> - Create a Launchpad Account.
[20:11] <SergioMeneses> You will  need a launchpad account because it is a very important tool on our testing trip:
[20:12] <SergioMeneses> a Launchpad account is needed for Reporting bugs, Question and Answers, Translations, Blueprints and even more! :) (imho: launchpad rocks!).
[20:12] <SergioMeneses> Then you need to sign the Ubuntu Code of Conduct and commit yourself to comply with it.
[20:12] <SergioMeneses> here is were to get started: https://login.launchpad.net/+new_account,
[20:13] <SergioMeneses> And here is an example on what you will get at the end: https://launchpad.net/~sergiomeneses.
[20:13] <primes2h> - Create a Personal Wiki Page.
[20:14] <primes2h> A personal wiki page is needed to let us know something about you, your goals and expectations about ubuntu, even something funny.
[20:14] <primes2h> It’s just a way to know each other and personal skills.
[20:14] <primes2h> And here is an example of a personal wiki page: https://wiki.ubuntu.com/SergioMeneses
[20:15] <letozaf> - Join the Ubuntu Laptop Testing Team \o/
[20:15] <letozaf> You must join  our team: https://launchpad.net/~ubuntu-laptop-testing
[20:16] <letozaf> and our mailing list: ubuntu-laptop-testing@lists.launchpad.net
[20:16] <letozaf> Remember also to join ubuntu-quality mailing list, ubuntu-quality@lists.ubuntu.com to keep informed about general testing related stuff.
[20:17] <SergioMeneses> - Set up an Hardware Profile
[20:17] <SergioMeneses> A hardware profile is needed to know the details of the hardware you are testing on.
[20:17] <SergioMeneses> This will allow people to know on what hardware Ubuntu works fine and also help developers fix bugs in case you find one or more during testing.
[20:18] <primes2h> There are two ways to do this:
[20:18] <primes2h> 1 - Automatic: you can create a profile on the ubuntu friendly website (graphic mode).
[20:18] <primes2h> 2 - Manual: you can share your hardware profile on a wiki page.
[20:19] <primes2h> Theoretically the first one should be the easiest way, because you can automatically obtain a complete hardware profile of your laptop.
[20:19] <primes2h> However, the inner limitations of the tools used, makes this method the long-lasting and less practical one for now.
[20:20] <letozaf> Briefly speaking, you need to run checkbox  from the stable release previous to the development image you are going to test.
[20:20] <letozaf> This way you are bound to perform a full system testing.
[20:21] <letozaf> Checkbox is pre-installed in Ubuntu and you will find it searching “System Testing” in the Dash.
[20:21] <letozaf> Finally, providing your launchpad email, you can submit results and then, after some time (that can go from a few hours to some days) you’ll find your hardware profile on the Ubuntu Friendly website: https://friendly.ubuntu.com/.
[20:21] <letozaf> This is how your laptop will look like in Ubuntu Friendly:
[20:22] <letozaf> https://friendly.ubuntu.com/12.04/Hewlett-Packard/HP%20G62%20Notebook%20PC/i:BZI:NyVHp:BI:I8g:BV6:BFCp:GzC:BEG:BV6:BFCp:h:B5G:DNO:BFC/
[20:23] <primes2h> We aim to simplify and improve the automatic process, so expect some news in the near future.
[20:23] <primes2h> That said , we are  going to explain the manual method more extensively, as it’s the most practical way to do this:
[20:23] <primes2h> You have to create a subpage of your personal wiki page, where you’ll put all information about your laptop.
[20:24] <primes2h> For example: https://wiki.ubuntu.com/YourPersonalPage/LaptopMakeModel (this is a only a template).
[20:26] <SergioMeneses> An example of an existing personal profile to use as a guide is:
[20:26] <SergioMeneses> https://wiki.ubuntu.com/SergioMeneses/AcerAspire4750
[20:26] <SergioMeneses> Now we are going to take some information from our computer to fill in our wiki page:
[20:27] <SergioMeneses> Laptop make and model -  the output of the commands:
[20:27] <SergioMeneses> $sudo dmidecode -s system-manufacturer
[20:27] <SergioMeneses> and
[20:27] <SergioMeneses> $sudo dmidecode -s system-product-name
[20:28] <SergioMeneses> now, On Lenovo laptops you need also to run
[20:28] <SergioMeneses> $sudo dmidecode -s system-version
[20:28] <SergioMeneses> to get the first part of the model name.
[20:29] <SergioMeneses> Laptop hardware information - the output of the commands:
[20:29] <SergioMeneses> $lspci -v  → (pci devices)
[20:30] <SergioMeneses> $lsusb    → (usb devices)
[20:30] <SergioMeneses> (without any external device attached)
[20:30] <SergioMeneses> and then
[20:30] <SergioMeneses> $lshw -short  → (hardware list)
[20:31] <SergioMeneses> with all this information ,we fill our wiki page :) as you can see in the model
[20:32] <SergioMeneses> questions about this?
[20:32] <primes2h> Any Questions ?
[20:36] <SergioMeneses> ok, there is not questions right now :)
[20:36] <ClassBot> pleia2 asked: Are you testing development releases, or the versions of Ubuntu that have already been released?
[20:40] <primes2h> In fact we test both, but we are more focused on development releases	
[20:41] <SergioMeneses> by the way, you can find our testing progress here: http://iso.qa.ubuntu.com/qatracker/milestones/219/builds
[20:42] <SergioMeneses> as you can see, there are LTS versions and Daily versions :)
[20:42] <ClassBot> JoseeAntonioR asked: What do those $ signs at the beginning mean? Should I type them in the Terminal too?
[20:43] <letozaf> Noskcaj, that indicates the shell you do not have to type that in
[20:43] <letozaf> sorry I meant no
[20:44] <letozaf> that indicates the shell you do not have to type that in
[20:44] <letozaf> you just have to type what comes after that sign
[20:44] <letozaf> and press enter
[20:44] <letozaf> so, for instance you have to enter:
[20:44] <letozaf> lspci -v
[20:44] <letozaf> and press enter
[20:45] <ClassBot> balloons asked: So at the moment, I should manually create a profile for my computer for testing?
[20:46] <letozaf> Well it depends
[20:46] <letozaf> The quickest way is creating a wiki page with all the info about
[20:46] <letozaf> your laptops hardware
[20:46] <letozaf> and then putting the link to the wiki page in the testcase result
[20:47] <letozaf> so we know what hardware has been tested
[20:47] <letozaf> the other way is to use checkbox, but it takes
[20:47] <letozaf> much more time, even if maybe
[20:48] <letozaf> having all your hardware info in the Ubuntu Friendly site
[20:48] <letozaf> is better
[20:48] <SergioMeneses> https://friendly.ubuntu.com/
[20:49] <letozaf> thank you SergioMeneses
[20:49] <ClassBot> pleia2 asked: how do I know whether I should I contribute to laptop testing or regular iso tracker testing?
[20:49] <letozaf> Well they are two different ways to test and contribute to Ubuntu
[20:50] <primes2h> You can contribute to both of them
[20:50] <letozaf> Let's say that if you have a laptop
[20:50] <letozaf> it is a good idea to contribute as you will help Ubuntu work
[20:50] <letozaf> on many different hardware
[20:50] <ClassBot> There are 10 minutes remaining in the current session.
[20:51] <letozaf> whith laptop testing you help test Ubuntu on a particular hardware
[20:51] <letozaf> with ISO tracker testing you test the ISO, but it is not always tested on hardware but also on virtual machines
[20:51] <letozaf> so hardware independetn
[20:51] <letozaf> independent
[20:53] <letozaf> then if your hardware profile is in Ubuntu Friendly websit
[20:53] <letozaf> website people can have a look at what hardware Ubuntu works on
[20:54] <primes2h> So, if there are no more questions we will continue talking about the fun part: testing! on the second session at 21:00 UTC same channel
[20:55] <ClassBot> There are 5 minutes remaining in the current session.
[21:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/07/%23ubuntu-classroom.html following the conclusion of the session.
[21:02] <letozaf> Hello everyone!
[21:03] <letozaf> Welcome to the second session on laptop testing.
[21:04] <letozaf> So, after having set up everything as explained in the previous session  lets start the fun part: TESTING :D
[21:05] <letozaf> To start testing, first of all go to the Laptop Tracker website at http://laptop.qa.ubuntu.com/.
[21:05] <letozaf> You will have to choose a milestone from the list, for instance “Quantal Final”  or “Raring Cadence Week 2”,
[21:06] <letozaf> depending on what it’s available for testing (look at the “status” column  “Testing”  indicates  what has to be tested and  “Released” indicates what does not as it has been released)
[21:07] <letozaf> http://laptop.qa.ubuntu.com/qatracker
[21:07] <letozaf> Once you have chosen the milestone you will have to select the correct image that corresponds to your computer’s architecture from another list:
[21:08] <letozaf> http://laptop.qa.ubuntu.com/qatracker/milestones/248/builds
[21:08] <letozaf> So, for example, if you have a 64 bit laptop you need to click on the small icon (CD with a green arrow) next to the “Ubuntu Desktop amd64” product.
[21:08] <letozaf> After clicking on it, you’ll be on the ISO image download page.
[21:09] <letozaf> Click on the first link you find on the list and you will be able to download the ISO.
[21:09] <letozaf> There is a quicker way to do this using zsync, but maybe we will explain this later if we have time.
[21:09] <letozaf> Generally speaking, updated daily images of the current development release are found at http://cdimage.ubuntu.com/daily-live/current/.
[21:10] <primes2h> Once you have downloaded the image you have two options:
[21:10] <primes2h> 1 - Put the ISO on a DVD or a USB key and boot your laptop from them to perform testing in a “live environment”.
[21:11] <primes2h> 2 - Install the ISO on your laptop using a separate partition of you hard drive.
[21:11] <primes2h> If you are new to this, you don’t feel comfortable on partitioning your hard drive or you don’t have much time available to test, go for option number 1.
[21:12] <primes2h> In a live environment you can successfully run all scheduled testcases except the hibernate one (that needs a real installation to run).
[21:12] <primes2h> The second option needs a separate partition of you hard drive just for testing so you won’t mess up the existing Ubuntu that is already on it :-D
[21:13] <primes2h> Anyway remember that  installing a development release on a production machine is
[21:13] <primes2h> usually not recommended if you don’t know what you are doing, development releases can “break things”, so be careful.
[21:14] <letozaf> Once you have booted Ubuntu, it’s time to start testing!
[21:14] <letozaf> You need to go back to the Laptop Testing tracker at http://laptop.qa.ubuntu.com/
[21:14] <letozaf> and log in using your launchpad credentials, otherwise you will not be able to submit your test results.
[21:15] <letozaf> Reporting Results and Filling Testcases
[21:15] <letozaf> As you did before select the milestone (e.g. Raring Cadence Week 2), then click on  your architecture product link for example Ubuntu Desktop amd64.
[21:16] <letozaf> You will see list of testcases to carry out ordered by category  like: Audio, Connectivity, I/O and so on.:
[21:16] <letozaf> http://laptop.qa.ubuntu.com/qatracker/milestones/248/builds/29797/testcases
[21:17] <letozaf> If you want to be notified when new images are available for testing
[21:17] <letozaf> you can select the  testcase checkboxes you are interested in and then click on the subscribe button at the end of the page under “Actions”
[21:17] <letozaf> This way you will be notified by email when an image is ready for testing.
[21:18] <SergioMeneses> You now need to follow the testcase instructions and carry out the tests one by one reporting the results
[21:18] <SergioMeneses> (“Passed”, “Failed” or if it is taking long you click on “In progress” so others know that you are carrying out the test).
[21:19] <SergioMeneses> http://laptop.qa.ubuntu.com/qatracker/milestones/248/builds/29797/testcases/1467/results
[21:19] <SergioMeneses> In the machine field you must copy and paste the link to your hardware profile
[21:19] <SergioMeneses> the one you created on a wiki page we spoke about in the previous classroom session ( https://wiki.ubuntu.com/SergioMeneses/AcerAspire4750 )
[21:20] <SergioMeneses> If you select “Failed” you have to indicate one or more bug numbers reported on Launchpad otherwise you will not be able submit your result.
[21:21] <primes2h> Take a look here: https://wiki.ubuntu.com/Testing/Laptop/Procedures for more detailed information on what just said.
[21:22] <primes2h> you can find more information about testing at our wiki page:
[21:22] <primes2h> https://wiki.ubuntu.com/Testing/Laptop
[21:22] <primes2h> and you can meet us in #ubuntu-quality on the Freenode network.
[21:23] <letozaf> Remember: The Laptop Testing Team is open to anyone who would like to provide  important hardware information about their laptops and help us make Ubuntu work on a wide range of hardware,
[21:26] <letozaf> We spoke about how getting the ISO for putting it on a live USB key or a DVD
[21:27] <letozaf> the best way to download an ISO is using zsync
[21:27] <letozaf> Zsync is very practical and fast for downloading ISO’s as it downloads only the parts of a file that are changed, so as to avoid downloading a full copy every time.
[21:28] <letozaf> Since the daily ISOs generally change quite little, it can be processed quite quickly
[21:28] <letozaf> zsync also performs a checksum comparison making it possible to change the flavour of the ISO (e.g. you have an ISO of Ubuntu and you want to change it on Kubuntu. Simply copy/paste the right line for Kubuntu and it will download just the parts that differs from the two versions).
[21:29] <letozaf> Ubuntu archives provide .zsync files using quite similar URIs about the various flavours. For example:
[21:29] <letozaf> zsync http://cdimage.ubuntu.com/daily-live/current/raring-desktop-i386.iso.zsync
[21:30] <letozaf> will sync the server's daily unstable raring (13.04) desktop image (for i386) to your local system with an older desktop image already stored on your hard drive.
[21:31] <letozaf> For more information on how to use it go to:
[21:31] <letozaf> https://help.ubuntu.com/community/ZsyncCdImage
[21:32] <letozaf> has anyone got questions ?
[21:38] <primes2h> There are no questions, so thanks a lot to all you guys!
[21:38] <primes2h> We hope to see you soon
[21:38] <letozaf> primes2h, there is a question
[21:41] <ClassBot> balloons asked: When do you plan to have a testing event again?
[21:43] <SergioMeneses> balloons, I think when the ubuntu-classroom-team invite us again :D
[21:43] <primes2h> Soon. 12.04.2 is on the way and
[21:44] <primes2h> and as soon as Raring beta1 is approaching
[21:45] <primes2h> we'll start do extensive  testing
[21:49] <ClassBot> pleia2 asked: Are there recommended times to do testing, or can I just download an ISO any random night I have time and give it a try? :)
[21:50] <primes2h> In general you can use this cadence reference page if you need to : https://wiki.ubuntu.com/Testing/Cadence
[21:50] <ClassBot> There are 10 minutes remaining in the current session.
[21:51] <primes2h> but the best is to subscribe yourself for email notification in the laptop tracker
[21:51] <primes2h> so you'll be notified when a new image is ready to be tested.
[21:52] <letozaf> if you look at the laptop testing tracker
[21:53] <letozaf> the status column tells you if we are currently testing
[21:53] <letozaf> or if it has been released
[21:54] <letozaf> so until you find the testing status you can test, then when testing is over you will find
[21:54] <letozaf> the status "released"
[21:55] <ClassBot> There are 5 minutes remaining in the current session.
[21:58] <primes2h> I think there aren't more question. So thanks a lot to you guys! I hope to see you soon
[21:59] <letozaf> bye to everyone and come and join the fun on the laptop testing team
[21:59] <SergioMeneses> ok guys thanks for coming :D
[21:59] <letozaf> :)
[21:59] <SergioMeneses>  \o/
[21:59] <primes2h> :-)
[21:59] <SergioMeneses> and thank to the Ubuntu Classroom Team: pleia2 and JoseeAntonioR
[21:59] <letozaf> yes thank you to pleia2 and JoseeAntonioR and balloons too
[22:00] <primes2h> Agree, thanks to all
[22:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/07/%23ubuntu-classroom.html