philip_linuxThough I'm late for the class, thanks Noskcaj, very good lessons for me :)08:51
philip_linuxI read the class in my history~~08:51
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Using your preferred testing system with Test Cases - Instructors: smartboyhw - Slides: http://is.gd/TlzUq5
smartboyhw[SLIDE 1] Oh hello, good morning (if you are in the USA0, good afternoon (in UK) and good evening (in Asia)!13:01
ClassBotSlides for Using your preferred testing system with Test Cases: http://people.ubuntu.com/~smartboyhw/Ubuntu_ISO_Testing_CLASSROOM.pdf13:01
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html following the conclusion of the session.13:01
smartboyhwI'm Howard Chan (smartboyhw).13:01
smartboyhwTo ask questions, please use the prefix "QUESTION:" to ask your question in #ubuntu-classroom-chat.13:02
smartboyhwWe have slides this time, so do read along with me:)13:02
smartboyhw[SLIDE 2] So, who am I?13:02
smartboyhwI'm a Ubuntu QA tester, and I like ISO Testing very much13:03
smartboyhwI'm also Ubuntu Studio's Release Manager, responsible for things like making release notes, etc.13:03
smartboyhwAt the same time, I'm a packager at Kubuntu.13:03
smartboyhw[SLIDE 3] OK, so here's a critical question: Why do we DO ISO testing?13:04
smartboyhwWell, what is the first thing you need to do when you want to use or try Ubuntu?13:04
smartboyhwDownload one of our images from the servers, burn it to a DVD or USB, and boot it up!13:04
smartboyhwHowever, what if the images just aren't working? The users will get angry and won't use Ubuntu.13:05
smartboyhwThis is what we NOT want.13:05
smartboyhwAs ISO testers, we always want to make sure we do make the images usable and installable.13:05
smartboyhwWe try to make it bug-free as most as possible. Of course, there might be some bugs that users find when we didn't find it.13:06
smartboyhwHowever, we seriously want most users to be able to try out and install Ubuntu.13:06
smartboyhw[SLIDE 4] Now, you need some utilities before doing ISO testing.13:07
smartboyhwFirst of all, it is a Launchpad account.13:07
smartboyhwIf you attended balloons' session, you would have learnt the importance of a Launchpad account. It is used to login across our QA Trackers, in this case, the ISO QA Tracker, in iso.qa.ubuntu.com13:07
smartboyhwThen, you need a SPARE machine (DON'T USE YOUR DAILY MACHINE) or a Virtual Machine.13:08
smartboyhwThese are needed to boot and test the images. I will talk about what kinds of Virtual Machines you can install later.13:08
smartboyhwPreferably, you should also have a Ubuntu system.13:09
smartboyhwYou don't have to necessary install our development release (Saucy Salamander), however it is good to do so.13:09
smartboyhwIt's also OK to use Windows or Mac OS X machines (better still for Macs as you can try out the amd64+mac) images13:10
smartboyhwAnd you must have an image:)13:10
smartboyhwFor example, if you want to test the Ubuntu Desktop amd64 image, you have to download it.13:10
smartboyhwI will teach you what is the best way to download an image later.13:11
smartboyhwSo, virtual machines.13:11
smartboyhwThere are multiple kinds of Virtual Machines' software in Ubuntu's archive.13:12
smartboyhwI like to use VirtualBox, as it is fully open-source and can test images easily13:12
smartboyhw[SLIDE 5] it's available by launching a terminal and type "sudo apt-get install virtualbox"13:12
smartboyhwA software I would recommend for beginning testers though is Testdrive13:13
smartboyhwTestdrive is a utility developed originally by Canonical, then Ubuntu QA Team got more involved in the development process this cycle.13:14
smartboyhwIt helps you to zsync (download and check) the image and launches the image using KVM or Virtualbox, all at one place13:14
smartboyhw"sudo apt-get install testdrive" and it's there for you!13:15
smartboyhwAlso available is Virt-manager (KVM)13:15
smartboyhwA kernel-based virtualization software, it's great also.13:16
smartboyhw[SLIDE 6] there are also some things I would recommend you to do.13:16
smartboyhwOne is to install zsync.13:16
smartboyhwzsync is a tool to download and check the md5sum of the image you downloaded.13:19
smartboyhwVery useful, if you don't want to re-download the image again.13:19
smartboyhwAll the above utilities have specific classroom sessions done by our QA Team members.13:19
smartboyhwFind the one you want in https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy13:19
smartboyhwAlso, I recommend you to make a hardware profile13:20
smartboyhwSo when a bug appears and is specific to your hardware, bug triagers and developers can fix it accordingly to your hardware.13:21
smartboyhwRead the instructions in https://wiki.ubuntu.com/QATeam/Hardware to make your own hardware profile. Shouldn't take more than a minute:)13:21
smartboyhw[SLIDE 7] What sorts of images should I test?13:22
smartboyhwBasically, EVERYTHING.13:22
smartboyhwIn some cases though, some images are more equal than others. :P13:22
smartboyhwLast week, we did some Alpha 1 testing on Kubuntu Desktop amd64&i386 images, Lubuntu Desktop & alternate ppc, mac, amd64 and i386 images13:23
smartboyhwUbuntu GNOME and UbuntuKylin images13:23
smartboyhwThese are to be released to the general public13:23
smartboyhwSo, these images would get tested before the others.13:24
smartboyhwIt doesn't really matter what image you test though.13:24
smartboyhwFor example, you don't like Ubuntu with Unity, you like it with KDE.13:24
smartboyhwSo you test Kubuntu images!13:24
smartboyhwIf you have a Mac machine, test the amd64+mac images!13:25
smartboyhwAfter testing one image, test another!13:25
smartboyhwMake sure you don't test images not fitting your computer's architecture.13:26
smartboyhwFor example, don't test an amd64 image in an i386 computer.13:27
smartboyhwIt will fail, and it is an invalid bug:)13:27
smartboyhw[SLIDE 8] So, here's my computer spec13:29
smartboyhwCompaq Presario CQ41-203TX Notebook13:30
smartboyhw4GB RAM, 1st-gen i513:30
smartboyhwRunning Ubuntu Saucy13:30
smartboyhwUsing Virtualbox 4.2.10 to test image 20130625 (shouldn't exist now, please zsync to the latest one)13:30
smartboyhwSo first of all, zsync to the the image you want to test.13:31
smartboyhw[SLIDE 8] for example, if you want to test the amd64 desktop Ubuntu image, run “zsync13:32
smartboyhw"zsync http://cdimage.ubuntu.com/daily-live/current/saucy-desktop-amd64.iso.zsync"13:32
smartboyhwShould take about 20 minutes if your connection is adequate:)13:33
smartboyhwSeriously, no questions? Don't be afraid to ask!13:34
smartboyhwWill stop for 5 minutes here, so you can zsync the image.13:36
smartboyhwGo to the ISO QA Tracker at http://iso.qa.ubuntu.com13:41
smartboyhwClick the login button and login using your Launchpad credentials (don't be scared by the Ubuntu One brand name:P)13:41
smartboyhwGo to "Saucy Daily"13:43
smartboyhwand click on the image you are testing13:43
smartboyhwFor example, "Ubuntu Desktop amd64" for me.13:43
smartboyhwSo, on that page there are many testcases13:44
smartboyhwBut for me, I want to run a testcase that will install Ubuntu within a single disk13:45
smartboyhwSo "Install (entire disk)" then13:45
smartboyhwClick at it, and you will enter a testcase page.13:46
smartboyhwClick at the "testcase" tab13:46
smartboyhwLook through the testcase.13:46
smartboyhwDo ask in #ubuntu-classroom-chat using QUESTION: if you don't understand the testcase.13:46
smartboyhwSo, let's begin.13:47
smartboyhwBoot up the image.13:47
smartboyhwFor me, it's Virtualbox.13:47
smartboyhwMy VM has 1GB RAM only:)13:48
smartboyhwIf you aren't following me with the same image no worries:)13:50
smartboyhwJust follow through the testcase.13:51
smartboyhwAfter all, our session is about "Using your preferred testing system with Test Cases"13:51
smartboyhwNow, I booted up the image, and it shows the nice screen, telling me to choose "Try Ubuntu" or "Install Ubuntu"13:51
smartboyhwThe testcase tells me to click "Install Ubuntu", so I shall follow it.13:52
smartboyhwStep 3.13:53
smartboyhwFortunately, all the boxes are in green ticks13:53
smartboyhw\o/ actually:P13:54
smartboyhwFor the plugins and install updates ticks, it doesn't really matter. I do tick those when I test the image.13:54
smartboyhwSo "Contineu" to step 5.13:55
smartboyhwThere goes the "Installation type" screen.13:55
smartboyhwThe "Erase disk and install Ubuntu" radio button should be default.13:55
smartboyhwIn this case, we want it;)13:56
smartboyhwSo click "Install now"13:56
smartboyhwWe only have 1 drive, so onto step 10.13:56
smartboyhwThe timezone (if you have a valid internet connection) should be set to your city13:57
smartboyhw(Or at least, your country/region's main city"13:57
smartboyhwClick "Continue"13:58
smartboyhwStep 12: I have to check if the keyboard is correct.13:58
smartboyhwIt is! English (United States)13:58
smartboyhwSo "continue"13:58
smartboyhwStep 14, the details screen.13:58
smartboyhwI entered the details13:58
smartboyhwAnd clicked "continue"13:59
smartboyhwNow, wait for the installation to continue. The slideshow should appear.13:59
smartboyhwI mean, the installation slideshow featuring new features of 13.04 (not 13.10, the responsible guys hasn't made it yet)13:59
smartboyhwNow, if you have any bugs, do report it.14:00
smartboyhwlaunch a terminal by pressing Ctrl+Alt+T14:00
smartboyhwFor the installer, type "ubuntu-bug ubiquity"14:00
smartboyhwIf you can't boot the image itself, type "ubuntu-bug syslinux"14:01
smartboyhw(Of course, in this case, type it in your host computer)14:01
smartboyhwIf there are graphics problems, type "ubuntu-bug xorg"14:01
smartboyhwMake sure you login using your Launchpad account, and provide enough details.14:01
smartboyhwSee https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs14:02
smartboyhwIt's for reporting bugs in a VM.14:02
smartboyhwDon't worry if you're unsure, just report it. Bug triagers will help determine if the bug is valid:)14:03
smartboyhwGuys, don't be afraid to ask questions, raise it up in #ubuntu-classroom-chat with prefix "QUESTION: "14:05
smartboyhw[SLIDE 21] Now the installation finished for me14:07
smartboyhwI clicked "Reboot now"14:07
smartboyhwIt asks you to remove the installation media14:07
smartboyhwPress "enter"14:07
smartboyhwit should reboot.14:08
smartboyhwAnd when it reboots, it will show a beautiful Ubuntu login scren!14:08
smartboyhwLogin and the Unity should appear:)14:09
smartboyhwOK, now, back into the ISO QA Tracker.14:11
smartboyhw[SLIDE 24] It's time to report our result14:11
smartboyhwSorry guys,14:14
smartboyhwgot someproblems with my computer14:14
smartboyhwBack to the results14:15
smartboyhwIf it is a pass, click Passed14:15
smartboyhwFail = "Failed"14:15
smartboyhwFor failed results, input the bug number of the bug you reported into the "Critical bugs" section14:15
smartboyhwIf it passed but still has bugs, input in the "Bugs" section14:16
smartboyhwLeave a comment on how it works14:16
smartboyhwAnd also, input the hardware profile link you pastebined earlier using the wiki page's instructions.14:17
smartboyhwClick "Submit result"14:17
smartboyhwThat's it!14:17
smartboyhw[SLIDE 26] There are some special images you can pay attention to.14:18
smartboyhwPowerPC images14:18
smartboyhwThese images are normally under-tested.14:18
smartboyhwHowever they exist for Ubuntu, Lubuntu and Kubuntu.14:18
smartboyhwIf you have a PowerPC computer (like the Apple G3 or G5), do help!14:19
smartboyhwUbuntu Touch Images.14:20
smartboyhwballoons, I think you should weigh in on this one...14:20
ClassBotSkini151 asked: If my VM results is different from real machine results, what should i do in this case?14:21
smartboyhwSkini151, well, if it's unreasonable for the results of one machine to happen in the other, report a bug.14:22
smartboyhwEven the same machine, Skini15114:22
smartboyhwTreat a Virtual Machine a bit independent.14:23
smartboyhwBTW, only use VMs in alpha testing.14:23
smartboyhwFor Betas and Release Candidates, we want REAL machines.14:23
smartboyhwballoons, can you talk about the Touch images please?14:23
balloonsUbuntu Touch Images are produced by the phablet team for a series of nexus devices14:24
balloonsoriginally based on quantal the images have been updated to raring and now saucy :-)14:25
balloonsYou can find a series of testcases designed around the images that are specific to each piece of nexus hardware14:25
smartboyhwThe devices are Samsung Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10.14:25
balloonsDownloading and installing a ubuntu touch image on one of the devices requires a few things14:26
balloonsyou need to ensure the bootloader is unlocked first, which is a one time step14:26
balloonsOnce unlocked you can install anything you wish on the device, including restoring android if you wish :-)14:27
balloonsthe phablet team maintains a ppa of tools for flashing here:14:28
balloonssudo add-apt-repository ppa:phablet-team/tools14:28
balloonsyou can then install sudo apt-get install phablet-tools android-tools-adb android-tools-fastboot in order to get the adb bits you need along with the phablet-tools created by the team14:28
balloonsrunning phablet-flash will then enable you to flash the device, and keep it up to date with new images14:29
balloonsFull details on installing on a device can be found here: https://wiki.ubuntu.com/Touch/Install14:29
smartboyhwThanks balloons :)14:29
smartboyhwThen, off to mininal installation images14:30
smartboyhwThese are called mini.iso images14:30
smartboyhwThey don't reside on our normal daily image repository in cdimage.ubuntu.com14:30
smartboyhwInstead, they reside on archive.ubuntu.com14:30
smartboyhwSince they are built off from one package: debian-installer14:30
smartboyhwThese images are the minimal environment you needed to install Ubuntu.14:30
smartboyhwYou can use tasksel to install whatever you want. Ubuntu + Kubuntu + Lubuntu is possible14:31
smartboyhwAnd finally, flavour images.14:31
smartboyhwOfficial flavours are those distributions that are based off from packages within the Ubuntu archie14:31
smartboyhwThey are: Kubuntu, Edubuntu, Xubuntu, Ubuntu Studio, Mythbuntu, Lubuntu, Ubuntu GNOME and UbuntuKylin14:32
smartboyhwThese flavours are always under-manpower14:32
smartboyhwEspecially when it's time to test images14:32
smartboyhwA normal QA tester doesn't only test Ubuntu images, he/she also spends testing time on these flavours too.14:33
smartboyhwso, help them! Go to their development IRC channel and subscribe to their development mailing list.14:33
smartboyhwThat's a kickstart point.14:33
smartboyhwOK, so some hints14:37
smartboyhw[SLIDE 27] If you see testcases that are marked "Mandatory", run these first.14:37
smartboyhwThese are very important testcases.14:38
smartboyhwThen run the "Run-once"14:38
smartboyhwFinally the "optional"14:38
smartboyhwDon't hesitate to report any bug you find, even if it doesn't make sense to others.14:38
smartboyhwTry run some testcases at the same time.14:38
smartboyhwFor example, do the "Live session" with the "Install (entire disk)"14:39
smartboyhwThese testcases don't contradict:)14:39
smartboyhw[SLIDE 28] We have some useful resources14:40
ClassBotSkini151 asked: When will start beta testing?14:40
smartboyhwFor Ubuntu, it will only participate in Beta 2 and RC, so that will start around 25th September.14:41
smartboyhwHowever most (if not all) flavours will participate in Beta 114:41
smartboyhwWhich is 3 weeks earlier14:41
smartboyhwThe resources:14:41
smartboyhwThis is a guide to test ISO images. It also includes a link to balloons's video on testing.14:42
smartboyhwContact us through ubuntu-quality@lists.ubuntu.com (do subscribe to us) and also through IRC in #ubuntu-quality14:43
smartboyhwThat's it for today, we hope to see you guys next time!!! And PLEASE help us to test ISO images!!!14:44
ClassBotThere are 10 minutes remaining in the current session.14:50
ClassBotThere are 5 minutes remaining in the current session.14:55
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html15:00
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || No Sessions Currently in Progress
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Installing and Introduction to bzr - Instructors: chilicuil
chilicuilHello everyone, my name is Javier Lopez: http://wiki.ubuntu.com/~chilicuil16:01
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html following the conclusion of the session.16:01
chilicuilI'm here today to talk a little bit about bzr and its correlation with the Ubuntu QA team16:01
chilicuilbzr usage is not limited to the QA team, virtually every Ubuntu team depends on it16:01
chilicuilso having a clue of how to use it proves helpful in the case you're interested in joining the Ubuntu family16:02
chilicuiltechnically bzr (or bazaar) is a distributed revision control system16:02
chilicuilDRCSs are systems which allow you to manage the storage and distribution of files (mostly code) to many people16:02
chilicuilwhen using a DRCS you get automatic backups, ease to modify files of different persons, freedom to experiment, and more good things, http://en.wikipedia.org/wiki/Distributed_revision_control16:03
chilicuilbzr is only one alternative of the many DRCSs available today, other choices are: git, hg, darcs, etc16:03
chilicuilin Ubuntu almost all source packages can be fetched from bzr16:03
chilicuiland in the QA team, we maintain and develop the Ubuntu testcases with bzr16:04
chilicuilI'll continue with a focus in the QA activities and some practical examples16:04
chilicuilif you don't understand any step or technical word please let me know and I'll be happy to stop and try to explain16:04
chilicuilso, let's take this case, you've had wonderful evenings using Ubuntu and now you're interested in giving something back to the community16:05
chilicuilyou've joined the QA team and decided you want to help with the Ubuntu manual testcases suite16:05
chilicuilthis example however will work if you're interested in helping in other areas, docs, code, or design -- as far as a project gets tracked by launchpad16:05
chilicuilsince you're starting you probably just wanna take a look and see if there's anything wrong such as a typo or a bad redaction16:05
chilicuilon this scenario you will eventually reach https://launchpad.net/ubuntu-manual-tests , and more specifically, https://code.launchpad.net/ubuntu-manual-tests16:06
chilicuilthere you'll see instructions to download full source code (hint: bzr branch...), and a list of branches16:06
chilicuilthose branches are differentials between the official source code (lp:ubuntu-manual-tests) and the branches themselves (e.g. lp:~noskcaj/ubuntu-manual-tests/parole)16:06
chilicuilso, let's start by downloading the code:16:06
chilicuil    $ bzr branch lp:ubuntu-manual-tests16:07
chilicuilif you don't have bzr, you'll need to install it, or ssh ubuntu@vps.javier.io, pass=ubuntu16:07
chilicuil    $ sudo apt-get install bzr16:07
chilicuilwhile the above command finish, we'll inform bzr who we are16:07
chilicuilwe do this to allow bzr write complete reports about who changed what in our projects, we also do it because bzr will reject to work if we don't complete this information =P16:08
chilicuil    $ bzr whoami "Your Name <your.mail@domain.com>"16:08
chilicuilonce the bzr branch command finish, you'll see a 'ubuntu-manual-tests' directory, there you'll have the whole project16:09
chilicuilinside of it, if you execute 'ls -lah', you'll notice a .bzr directory16:09
chilicuilthe .bzr directory is the place where all the bzr information is saved, it's better not to play with it16:10
chilicuilso, now that we have the code, we can start by taking a look at the files and history, we can see what changes had been done and by whom over the time16:10
chilicuil    $ bzr log | less16:10
chilicuiland you'll see a couple of interesting fields16:10
chilicuilmy output looks like this: http://sprunge.us/XjFK16:11
chilicuil  * revno (aka revision): these numbers are spots where specific changes were done and saved, for example, we can go and see how this repository looked at revno #1 and go back to compare with the current status16:11
chilicuilin other terminal, go to the 'ubuntu-manual-tests' directory and execute:16:12
chilicuil    $ bzr revert -r1 #you'll see a list of files who were modified, added or removed, compared to the last version16:12
chilicuil    $  ls testcases/packages/ | wc -l16:12
chilicuil    2416:12
chilicuil24 is the number of tests and dirs the package section had when the project was exported for the first time to launchpad16:13
chilicuilnow, if we go back to the present16:13
chilicuil    $ bzr revert16:13
chilicuil    $ ls testcases/packages/ | wc -l16:13
chilicuil    5016:13
chilicuilyou'll see there has been a progress =), so bzr and DRCS are like time machines for files, you can go to any of the revision number and see how it looked at that moment16:13
chilicuilthere are more interesting information in the 'bzr log | less' command16:14
chilicuil * committer: the person which introduced a revision (or whom to blame =P)16:14
chilicuil * branch nick: the name of the tree of changes, yep, you can have different trees with full revisions stacks @_@16:14
chilicuil * timestamp: change time16:14
chilicuil * message: a description of the change16:14
chilicuilso, now that we've looked around, we could review the current files and see if we can find anything wrong16:15
chilicuillet's open "testcases/packages/1424_Nautilus\ Tests"16:15
chilicuilif we look at it you'll see that this file have an specific format (more of it in the next session)16:15
chilicuilright now we're only change some references from Nautilus to Files, as you know Nautilus was renamed to Files and this testcase hasn't been updated16:16
chilicuillet's do it, change every reference from Nautilus to Files, I'll wait a couple of minutes16:16
chilicuilnow we can see our changes by running:16:20
chilicuil    $ bzr diff16:20
ClassBotThere are 10 minutes remaining in the current session.16:21
chilicuilmine looks like this: http://sprunge.us/SKAb16:21
chilicuilThe '-' list the old data while the '+' show the updated information, if everything looks ok, we can create one of those nice snapshots in time called revno or revisions16:21
chilicuil    $ bzr commit -m "description here"16:21
chilicuil    ...16:21
chilicuil    Committed revision 14316:21
chilicuilafter doing it, if you run: bzr diff, this time bzr won't print anything, this happens because our changes have been saved and we're currently in the head of the tree16:21
chilicuilthis doesn't mean we won't be able to view again what our changes were, we can look at them (again) if we run:16:21
chilicuil    $  bzr diff -r142..143 #143 was our revision16:22
chilicuilthe same command can be run to know the changes between two random revisions16:22
chilicuilnow, let's imagine that during our edit session we wrote Fils instead of Files in one of the many Nautilus changes16:22
chilicuilin that case, we can uncommit our work, fix the botched job and commit it again:16:22
chilicuil    $ bzr uncommit16:22
chilicuil    # fix the typo16:22
chilicuil    $ bzr commit -m "Description"16:22
chilicuilNow we're in a stage where our work can be shared with others16:22
chilicuiltill now, we've only modified local files and the snapshots had been taken in our system16:22
chilicuilso, the first step to do is to upload our branch to lp16:22
chilicuilhowever in order to communicate with launchpad we need to setup our ssh public key(s): https://launchpad.net/~chilicuil/+editsshkeys16:23
chilicuilif you don't have a ssh key, you can create one with the following command:16:23
chilicuil    $ ssh-keygen #and pressing enter till you get back the terminal prompt16:23
chilicuilafter exporting your ssh key, you'll need to tell launchpad who you are:16:23
chilicuil    $  bzr launchpad-login your_nickname16:23
chilicuilif you completed these two steps, you'll be able to communicate safety with lp, let's upload our changes:16:23
chilicuil    $ bzr push lp:~chilicuil/ubuntu-manual-tests/rename-nautilus-to-files16:23
chilicuilas you can see, the path we're using to push the files is not random16:23
chilicuilfirst, it has our username associated, ~chilicuil, after that, it's the name of the project we want to contribute, in this case it is 'ubuntu-manual-tests', and finally it has a name we selected for our branch16:23
chilicuiltake in consideration that if you look at http://help.launchpad.net, you could see references to 'junk' branches16:23
chilicuilfor example here: https://help.launchpad.net/Code/PersonalBranches16:24
chilicuil    $ bzr push ~chilicuil/+junk/rename-nautilus-to-files16:24
chilicuilthe syntax is very similar, however when uploading to junk branches you won't be able to request merges (that is the possibility to copy your changes to another project)16:24
chilicuilt's a common mistake to upload to a junk branch when what you really want is to upload and then request a merge16:24
chilicuilso, finally, if your code has been imported, you can request a merge by using the command:16:24
chilicuil    $ bzr lp-propose #or going directly to your branch in launchpad and select 'Propose for merging'16:24
chilicuilother people working in the same project will get your changes by branching the original project (where your changes will land) or using 'bzr pull' to update their branches with the 'master' tree16:24
chilicuilso basically that's how we work in the QA team16:25
chilicuilthere many other commands and ways to use bzr, and people in #ubuntu-quality is familizared with it, so feel free to join us and ask, there also good resources online:16:25
chilicuil * http://doc.bazaar.canonical.com/latest/en/mini-tutorial/16:25
chilicuil * http://doc.bazaar.canonical.com/bzr.2.5/en/16:25
chilicuilif you already know git, you can start here: http://doc.bazaar.canonical.com/migration/en/survival/bzr-for-git-users.html16:25
ClassBotThere are 5 minutes remaining in the current session.16:25
chilicuilI think that's all, any question?16:26
chilicuilok, if there is none, I'll end this session right now and will get back in 5 minutes to continue with the next one (ubuntu-manual-testcase collaboration) thanks a lot for following the session (or reading it later)16:29
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Creating and editing Manual Test Cases - Instructors: chilicuil
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html following the conclusion of the session.16:31
chilicuilI'm back =P!, on this session I'll talk about the ubuntu-manual-testcase suit and how to contribute to it16:33
chilicuilthis will be a full interactive session, so feel free to launch your terminal and get your launchpad credentials16:34
chilicuilI'll be doing live edition in ssh ubuntu@vps.javier.io pass=ubuntu, feel free to connect16:34
chilicuilthe ubuntu-manual-testcase: https://launchpad.net/ubuntu-manual-tests16:34
chilicuilis where the packages.qa.ubuntu.com and iso.qa.ubuntu.com testcases live16:34
chilicuilfrom lp they're exported to *.qa.ubuntu.com where are consumed by testers during the cadence weeks: https://wiki.ubuntu.com/Testing/Cadence/16:34
chilicuilit's an extremely easy way to get started with the Ubuntu family and more specifically with the QA team16:35
chilicuilif you followed the bzr session you'll already have an 'ubuntu-manual-tests' directory in you $HOME16:35
chilicuilif you didn't follow it, you can fetch the complete project with this command:16:35
chilicuil    $ bzr branch lp:ubuntu-manual-tests16:35
chilicuilonce you have the project, we can open any of the testcases16:35
chilicuilbut first let's go to: http://packages.qa.ubuntu.com/qatracker/milestones/281/builds/47603/testcases/1422/results16:36
chilicuiland then to 'Testcase' to see how testcases actually look when deployed16:36
chilicuilin my computer it looks like this: http://i.imgur.com/zo32w8l.png16:36
chilicuilnow, let's open the testcase file: testcases/packages/1424_Nautilus\ Tests16:37
chilicuilnow, you'll see that this file is mostly and html one16:38
chilicuilall manual testcases get differente sections, each one defined by the 'Test-case name: app/TC-SHORTCODE-NUMBER'16:39
chilicuilwhen creating a new testcase you don't need to worry by the testcase number, people will assign one to it once it gets merged16:40
chilicuilso, after the first line, which is Test-case name: nautilus/TC-NFM-001 (to define that what follows is the first test of the Nautilus testcase suite)16:41
chilicuilfollows a short description of what the test will try to prove, on this case it will try to verify if Nautilus (now Files) is able to create new files, which is a very basic feature expected from a file manager16:42
chilicuiltests can depends in others to test functionallities, for instance, if we're gonna write a test to check if Nautilus can change the name of a file, it can depend of the creation of that file, the sintax is: depends: app/TC-SHORTCODE-NUMBER16:44
chilicuilonce described the test, follows the actual steps to verify if the desired behavior works or not16:45
chilicuilas you can see it has an specific format, which is basically, dl tags for the complete test, <dt> tags for steps, and <dd> for expected results16:46
chilicuilwhen creating new manual testcases, it's recommended that you start by write down all the desired results and steps in plain text, and format it at the end16:48
chilicuilrequired testcases are filled as bugs in https://bugs.launchpad.net/ubuntu-manual-tests/+bugs, currently we're trying to test the functionallity of all default applications in Ubuntu and derived Ubuntu flavors16:50
chilicuilthat's why there are many new reports opened16:50
ClassBotThere are 10 minutes remaining in the current session.16:50
chilicuilfeel free to grab anyone if you feel confortable with the usage of one default ubuntu application16:51
chilicuilright now, I'll take a look at https://bugs.launchpad.net/ubuntu-manual-tests/+bug/118392916:51
chilicuilwhich is a report who tracks the status of the konsole testcase, konsole is the default X terminal emulator for KDE16:52
chilicuilwhen creating a testcase, you must do it in an ubuntu development version, right now in an ubuntu saucy env16:53
chilicuilyou can use virtualbox, an spare machine or a chroot to run safety the ubuntu dev version: https://wiki.ubuntu.com/UsingDevelopmentReleases16:54
chilicuilwhat I'll do right now is to open a new instance of pbuilder, $ sudo DIST=saucy ARCH=i386 pbuilder login16:54
chilicuilinstall konsole, and then run it16:54
chilicuilI'll take as a reference testcases/packages/1422_Gnome\ Terminal\ Tests16:55
ClassBotThere are 5 minutes remaining in the current session.16:55
chilicuilso if we go back to our online environment, you can see how I do it, I'll open both files, testcases/packages/1422_Gnome\ Terminal\ Tests and a new testecase file for Konsole, testcases/packages/Konsole\ Terminal\ Tests16:57
chilicuilso, I'll start by adding: Test-case name: konsoleterminal/kter-001 and then a description17:00
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html17:00
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || No Sessions Currently in Progress
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Creating and editing Manual Test Cases - Instructors: chilicuil
chilicuilfor now, I'll only complete the first testcase so I can show you how to send those changes to the ubuntu-manual-tests project17:09
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html following the conclusion of the session.17:10
chilicuilhowever the more detailed one testcase can be done the better17:10
chilicuilright now my testcase file looks like this: http://pastebin.ubuntu.com/5817338/17:11
chilicuilwhen we start working on a testcase it's a good idea to assign the report which tracks the status to ourselves17:11
chilicuilon this example, I'll assign the Konsole testcase to me, you can do it by going to the launchpad report and click the 'unassigned' button and then 'Assign me'17:12
chilicuilnow, going back to our tree if we run: $ bzr status17:13
chilicuilwe'll see that our file figures as: Unkown, that's because it has not been added to the tree, is a complete new testcase!17:14
chilicuilwe can add it by running: $ bzr add 'testcases/packages/Konsole Terminal Tests'17:14
chilicuiland then: $ bzr commit -m "New Konsole testcase"17:14
chilicuiland after adding to the local tree, we can share it to the world with: $ bzr push lp:~chilicuil/ubuntu-manual-tests/new-konsole-testcase17:17
chilicuilnow if you go to your launchpad profile, to the code section, https://code.launchpad.net/~ you'll see the branch you've just pushed17:20
ClassBotThere are 10 minutes remaining in the current session.17:20
chilicuilin my case it's here: https://code.launchpad.net/~chilicuil/ubuntu-manual-tests/new-konsole-testcase17:21
chilicuilso, I'm gonna propose the change and add a description, which may be as simple as: Adds Konsole Testcase17:21
chilicuilnow, it'll get review and probably approved by one of the testcase admins: https://code.launchpad.net/~chilicuil/ubuntu-manual-tests/new-konsole-testcase/+merge/17237217:22
chilicuilas we know that handling html tags can be troublesome, we created a script which will let you know if your testcase is ready for review: https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script17:23
chilicuilensure you run it before actually pushing to the ubuntu-manual-tests project17:24
chilicuilwe're always open to new contributors so if by any change you feel like contributing to the ubuntu-testcase suite join us at #ubuntu-quality and let us know17:25
chilicuilthere is also a nice tutorial step by step here: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual in case this session were horrible for you17:25
ClassBotThere are 5 minutes remaining in the current session.17:25
chilicuilQUESTION: how do I know what applications need tests?17:29
chilicuilright now we're focusing in the default ubuntu applications, you can get a full list here: https://bugs.launchpad.net/ubuntu-manual-tests/+bugs, you can assign any of them17:29
chilicuil QUESTION: How do I know what to test in my testcase?17:30
chilicuilat the beggining you can focus in the more obvious features, however the more detailed the better17:30
chilicuilwe intend to really improve the ubuntu quality17:30
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/07/01/%23ubuntu-classroom.html17:30
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || No Sessions Currently in Progress
=== bipul is now known as koolbrain17
=== koolbrain17 is now known as Dexter
=== Dexter is now known as Dexter_
=== emma is now known as em

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!