Re: Facebook Page
On 20/08/12 11:26, Phill Whiteside wrote: > there is on Facebook a subtle but important difference between open, > private & hidden. A private group is advertised to all, but requires > acceptance to join. The reason I chose private is that it does reduce > the attacks by spammers. As we all have better things to do than run > around cleaning up after spammers, that is why I chose private. I didn't know that, Phill, thanks for the info! So anyone can see what's going on as long as they have a FB user but they need to go through scrutiny (i.e. deciding if they are spammers) to join, right? Sounds good. In any case, I have decided to un-join the group in support of our users that cannot follow us in FB and my own conviction that it is not the right thing to do to have technical conversations there. I can spare myself the advertisement, since I follow things closely on IRC and mailing anyway. Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Facebook Page
On 19/08/12 16:14, Ho Wan Chan wrote: > We do need, I think, advertising for QA. I agree that we need advertising. I fail to see how a private group is going to do that for us. Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Facebook Page
On 17/08/12 23:01, Elfy wrote: > On 17/08/12 04:41, Phill Whiteside wrote: >> Hi guys & gals, >> >> as a part of Nicholas's questionaire one thing that had been >> previously discussed was how does QA advertise itself. We have bounced >> a couple of ideas about. One of them has actually arrived, albeit in a >> beta version. [1] Nicholas will quite easily say that he is not a >> FaceBook person, and in all honesty, I am only because of Lubuntu [2]. >> [3]. >> >> The group is 'permissive' so that only admins may accept new members, >> this has been previously shown to me to be effective in reducing spam >> attacks & I would like to keep to keep it that way. For this to >> continue we will need more admins! >> >> Hopefully there are other members of the QA group who are also >> familiar with looking after a fb group account. The banner will be >> done once we decide if we do decide to use FaceBook to improve our >> rating of "What, there, is a QA team?" score on the recent survey. >> >> I now retire and await for world war three to break out :) >> >> Nah, just joking, but please give your thoughts & if you think it will >> be useful as an area to introduce people to QA, have a chat, point new >> commers into QA, then please ask to be an admin. >> >> Thanks, >> >> Phill. >> 1. https://www.facebook.com/groups/432347580138081/ >> P.S. we need ~20 members to have the name changed from >> "432347580138081 >> <https://www.facebook.com/groups/432347580138081/>" to "Ubuntu QA" >> Please join :) >> 2. https://www.facebook.com/Lubuntu.Official.Page >> 3. https://www.facebook.com/groups/lubuntu.official/ >> >> >> >> -- >> https://wiki.ubuntu.com/phillw >> >> >> > Facebook ? > > What's that? > > (for the - wut? crowd ... ) > > As long as all these > > Social media things are in ADDITION to what we all ready have -= then +1 > > Of course - what we really need is an ARM place... > > Elfy > > > Hi, I have been thinking about this social media stuff to coordinate. I have mixed feelings, I particularly go through phases of hating facebook and stop using it completely, if we move all the communication there as opposite to email, I will miss good chunks. Facebook is not an open platform, there are no open archives for people that do not use facebook and we are forcing people basically to give their data away if they want to collaborate with us. There are others who their parents, rightfully in my opinion, keep away from facebook and other social media that may not be suitable for their age, and we would be excluding them from conversations. I think social media are good to share news with others, but are not the right place to have technical discussions. Cheers, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Testing removable media
Hey Jeff, On 15/08/12 14:07, Jeff Lane wrote: > Hey folks, > > I wanted to ask a quick and dirty question: > > What would you consider a "Stress" test of removable media like USB Keys > & SD/SDHC cards? What are you trying to test exactly, the speed of the HW itself or the throughput that you get from a particular driver/implementation? The file-system on that media? The time it takes to wear off? What is it that you are trying to stress? > > I'm working on enhancing a script and so far, the only idea put forth > was to do multiple simultaneous read/writes (like 100 at a time). But is > that a realistic stress test for something meant to be small, light but > with a very slow transfer speed? It all depends on what you are trying to achieve. There are many variables and there are file-system implementations that can interfere with your measurements. > Or would it be more appropriate to do something more realistic like, > transfer increasingly large files up to a pre-determined size (perhaps a > 2GB file size max?) Maybe for an SD card more realistic would be to transfer 3-4 MB files, but tons of them, like people do with cameras/music. Again back to my question of what you are trying to stress. Thanks, Gema > > Cheers, > > Jeff > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Questions about testing
On 14/08/12 12:17, Ho Wan Chan wrote: > You don't normally use Windows alongside Ubuntu Wubi in VMs, also then > the bootloader is better. Agreed, the usual use case here is a user on their PC installing from wubi from their windows. Same concerns apply, when doing this, back up your data! Gema > > 2012/8/14 Tobias mailto:k1...@gmx.de>> > > but wubi testing is preferred on real hardware, right?? > > > > > Am 14.08.2012 12:06, schrieb Gema Gomez: >> On 14/08/12 11:04, Ho Wan Chan wrote: >> >> >>> Mart, >>> >>> Use Gema's opinion: She's an official Canonical employee, while I am >>> only a active community tester... >> Hey, everyone's opinion count and is welcome! >> >> More than a canonical employee I am a QA Engineer, I have been for many >> years now, so I tried to give an explanation for a new comer from that >> viewpoint, I hope everyone can benefit from it and I am open to >> discussion if you guys think it may help. >> >> Thanks everyone for your help, >> Gema >> >>> 2012/8/14 Gema Gomez >> <mailto:gema.gomez-sol...@canonical.com> >>> <mailto:gema.gomez-sol...@canonical.com> >>> <mailto:gema.gomez-sol...@canonical.com>> >>> >>> Hi Mart, >>> >>> I disagree with Ho Wan Chan, here is my opinion. >>> >>> On 14/08/12 10:13, "Mart Küng" wrote: >>> > Hi >>> > >>> > I have a couple of questions about how to configure my machine >>> when testing. >>> > Is there a significant difference if any between testing in >>> virtual >>> > machine and installing on real hardware? >>> >>> On virtual machines you are testing some parts of Ubuntu. On real >>> hardware you are testing others, in fact, depending on which >>> hardware >>> you have, you are increasing our chances of finding problems for >>> your >>> specific HW, because we don't have infinite HW to test on. >>> Basically, >>> when you test on HW you are using drivers that noone else is >>> potentially >>> using. >>> >>> In the Platform QA Team in Canonical, we are testing with VMs for >>> the >>> daily ISO testing, and we test on a variety of HW the different >>> kernel >>> SRUs, so that we are reasonably confident that they will work on a >>> wide >>> variety of HW. >>> >>> Testing on HW is different from testing on VMs, both useful >>> depending on >>> what you are trying to achieve, since with ISO testing we are >>> trying to >>> cover as much HW as we can, testing on HW will be more useful from >>> that >>> viewpoint. >>> >>> > >>> > Would it be reasonable to dual boot version I'm testing with my >>> regular >>> > everyday system? I ask this because of my netbook: on my desktop I >>> could >>> > easily use virtual machine or change HDD-s. But netbook is to >>> weak for >>> > virtual machine and changing HDD seams to troublesome. >>> >>> You can dual boot your everyday system, but there are risks that an >>> installation goes wrong and you blow up your current system. That >>> is the >>> reason why we don't recommend it. If you are confident you know your >>> system and that won't happen to you, I still recommend you have >>> backups >>> of all the important documents before attempting the testing along >>> your >>> existing system. Other than that, it is very useful that you >>> install the >>> current version along an existing one, because many users will be >>> doing >>> just that, and we want them to be able to do it. >>> >>> >>> Thanks, >>> Gema >>> >>> > >>> > Mart >>> > >>> > >>> >>> >>> -- >>> Gema Gomez-Solano>> <mailto:gema.gomez-sol...@canonical.com> >>> <mailto:gema.gomez-sol...@canonical.
Re: Questions about testing
On 14/08/12 11:04, Ho Wan Chan wrote: > Mart, > > Use Gema's opinion: She's an official Canonical employee, while I am > only a active community tester... Hey, everyone's opinion count and is welcome! More than a canonical employee I am a QA Engineer, I have been for many years now, so I tried to give an explanation for a new comer from that viewpoint, I hope everyone can benefit from it and I am open to discussion if you guys think it may help. Thanks everyone for your help, Gema > 2012/8/14 Gema Gomez <mailto:gema.gomez-sol...@canonical.com>> > > Hi Mart, > > I disagree with Ho Wan Chan, here is my opinion. > > On 14/08/12 10:13, "Mart Küng" wrote: > > Hi > > > > I have a couple of questions about how to configure my machine > when testing. > > Is there a significant difference if any between testing in virtual > > machine and installing on real hardware? > > On virtual machines you are testing some parts of Ubuntu. On real > hardware you are testing others, in fact, depending on which hardware > you have, you are increasing our chances of finding problems for your > specific HW, because we don't have infinite HW to test on. Basically, > when you test on HW you are using drivers that noone else is potentially > using. > > In the Platform QA Team in Canonical, we are testing with VMs for the > daily ISO testing, and we test on a variety of HW the different kernel > SRUs, so that we are reasonably confident that they will work on a wide > variety of HW. > > Testing on HW is different from testing on VMs, both useful depending on > what you are trying to achieve, since with ISO testing we are trying to > cover as much HW as we can, testing on HW will be more useful from that > viewpoint. > > > > > Would it be reasonable to dual boot version I'm testing with my > regular > > everyday system? I ask this because of my netbook: on my desktop I > could > > easily use virtual machine or change HDD-s. But netbook is to weak for > > virtual machine and changing HDD seams to troublesome. > > You can dual boot your everyday system, but there are risks that an > installation goes wrong and you blow up your current system. That is the > reason why we don't recommend it. If you are confident you know your > system and that won't happen to you, I still recommend you have backups > of all the important documents before attempting the testing along your > existing system. Other than that, it is very useful that you install the > current version along an existing one, because many users will be doing > just that, and we want them to be able to do it. > > > Thanks, > Gema > > > > > Mart > > > > > > > -- > Gema Gomez-Solano <mailto:gema.gomez-sol...@canonical.com>> > Ubuntu QA Team https://launchpad.net/~gema.gomez > Canonical Ltd. http://www.canonical.com > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Questions about testing
Hi Mart, I disagree with Ho Wan Chan, here is my opinion. On 14/08/12 10:13, "Mart Küng" wrote: > Hi > > I have a couple of questions about how to configure my machine when testing. > Is there a significant difference if any between testing in virtual > machine and installing on real hardware? On virtual machines you are testing some parts of Ubuntu. On real hardware you are testing others, in fact, depending on which hardware you have, you are increasing our chances of finding problems for your specific HW, because we don't have infinite HW to test on. Basically, when you test on HW you are using drivers that noone else is potentially using. In the Platform QA Team in Canonical, we are testing with VMs for the daily ISO testing, and we test on a variety of HW the different kernel SRUs, so that we are reasonably confident that they will work on a wide variety of HW. Testing on HW is different from testing on VMs, both useful depending on what you are trying to achieve, since with ISO testing we are trying to cover as much HW as we can, testing on HW will be more useful from that viewpoint. > > Would it be reasonable to dual boot version I'm testing with my regular > everyday system? I ask this because of my netbook: on my desktop I could > easily use virtual machine or change HDD-s. But netbook is to weak for > virtual machine and changing HDD seams to troublesome. You can dual boot your everyday system, but there are risks that an installation goes wrong and you blow up your current system. That is the reason why we don't recommend it. If you are confident you know your system and that won't happen to you, I still recommend you have backups of all the important documents before attempting the testing along your existing system. Other than that, it is very useful that you install the current version along an existing one, because many users will be doing just that, and we want them to be able to do it. Thanks, Gema > > Mart > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Ubuntu 12.04 LTS not able to bootup on Hewlett Packard HP8560w notebook
On 11/07/12 08:27, TanTH7 wrote: > Dear Sir/Madam, > > If you have fix the below problem, let me know so I can > download the iso file again and verify the problem is gone now. Whenis > your best guess this bug is fixed and I can do testing again? Hope to > hear from you again. > > Dear tanth7, Are you sure you wanted to install server? It sounds to me as if what you are after is Ubuntu Desktop. In any case, I don't think you sent this email to the right list. When things fail, you are supposed to raise a bug on launchpad, adding as much information as possible so that a developer can look into it and fix it. A mailing list is not the right place to track this kind of issues. On this mailing in particular, we do manual testing and report bugs, but we are not responsible for fixing them, that is the task of the developers. You can read about how to raise a bug: https://help.ubuntu.com/community/ReportingBugs Once you have raised a bug, make sure to talk to some developers, or let bug-control know so that they can make the right developer aware of the problem: https://wiki.ubuntu.com/UbuntuBugControl/ Your problem doesn't sound so much as a testing problem, but as a bug that should be reported and dealt with. Once you've raised the bug, make sure you follow up with the developer (they may ask you for further logs, or to try a tentative solution) and if you collaborate, the bug will end up fixed. Thanks for taking the time to report the problem, and for helping make Ubuntu better! Gema > > Rgds,Tan TH tan...@gmail.com > > > > *From:*TanTH7 [mailto:tan...@gmail.com] > *Sent:* Thursday, July 05, 2012 2:12 PM > *To:* 'br...@ubuntu.com'; 'ubuntu-qa@lists.ubuntu.com'; > 'nixter...@ubuntu.com'; 'phi...@ubuntu.com' > *Subject:* Ubuntu 12.04 LTS not able to bootup on Hewlett Packard > HP8560w notebook > > > > Dear Sir/Madam, > > After downloading ISO file ubuntu-12.04-server-amd64.iso > obtained from http://www.ubuntu.com/download/server, the installation > was successful and complete on HP8560w computer. Upon boot-up, I > noticed that the graphics device driver has a failed error message after > which I cannot see the usual Ubuntu login screen. The sound is correct > for the login screen. Appreciate if you can check the graphics device > driver file to see if it is correct. Please help to forward to the > relevant person for him/her to attend if you are not the correct > person. Hope to hear from you soon. If you do need further > information, please do let me know. > > > > CPU: Intel(R)Core(TM) i7-2720QM CPU@2.2GHz <mailto:CPU@2.2GHz> > > System Type:64bit > > Display Adapters: Nvidia Quadro 1000M > > > > Rgds,TH Tan > > tan...@gmail.com > > > > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Tracking issues that we should be testing
On 06/06/12 13:58, Robie Basak wrote: > Hi, > > Every so often I come across an issue which I feel that we should be > testing on a regular basis. For example: I think that this multipath bug > should be considered for automated installer testing for Ubuntu Server: > > https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1004243 > https://lists.ubuntu.com/archives/ubuntu-server/2012-June/006321.html > > I think this kind of thing is a candidate for a consumer of UTAH, but > due to the d-i involvement required is perhaps not trivial to do right > now. > > Do we have a way of tracking these items so that we could have a backlog > of tests that we would like to have once the infrastructure is in place? > Perhaps a Launchpad project to add a bug task against? > > Thanks, > > Robie > Hi Robie, I have added a section at the bottom of this blueprint for this: https://blueprints.launchpad.net/ubuntu/+spec/qa-q-add-test-coverage Please add your explanation there and I will turn it into work items that will be implemented either this cycle or next, depending on resources availability. We are going to be reworking the installer testing this cycle and it makes sense probably to add this one as well. If you think the test case is important enough to be run on daily basis, as part of our smoke testing, add it here: https://blueprints.launchpad.net/ubuntu/+spec/qa-q-builds-smoke-testing Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Olivier Vermesse
Hi Olivier, > As suggested in the paragraph "How do I Get Involved?" on the wiki, let > me introduce myself. Before I begin, I want to apologize for my > English. I am French, and like all French people, I don't speek very > well in a foreign language ... :-) as a Spanish with problems with English, I hereby welcome you to the Ubuntu-QA group! > I'm 38 and I live in Montreux, Switzerland. For those who love jazz, > he must know this city ... > I am IT Engineer at Lausanne University Hospital and I particularly > like tested Ubuntu here. In short, I have time and would love to help you. > So if on one project or another, you need some help, I'm at your > disposal. Really. Good, because we need all the help we can get, we are releasing Precise next week and we need people motivated to go through installs some times and tell us if there are any problems. Do you have a launchpad user? If not, create an account for yourself in launchpad: https://launchpad.net/ Then, go to the iso-tracker (http://iso.qa.ubuntu.com/), and log in with your launchpad id, once you've done that you'll see Milestones, choose the one that is on Status "Testing". Then go down to the Ubuntu images, and depending on which hardware you have for testing, get started with the applicable product. For instance, if you have a 64 bit machine with some free HD space, you can go for Ubuntu Desktop AMD64, and in there you'll find a link to the latest build and some test cases. If you are going to use your own machine for this, be careful, it is easy to install on the wrong place and lose some data, if I were you I'd do a backup first. Please, make sure you record any test result in the test case you happen to run. You could run them in French to give us some coverage in your language. If you raise any bugs, please also note them down when you submit you result. Happy testing! Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Asus Eee PC 701/4G Laptop Testing Results
Hi Xelsior! On 19/01/12 21:43, Xelsior wrote: > Here are my testing results for the Asus Eee PC 701/4G. It is now > running really fast on my system ! It could do with a little more > memory for those who open a lot of tabs in Firefox. Can you tell us which test cases did you run? This email comes a bit out of context at least for me and cannot really understand what testing were you doing or with which objective. > > I am unsure what to do with this information now ... publish it on the > wiki ? It would be nice to see these kind of changes included as > Lubuntu runs really nicely on the 701. Regarding test results, unless you were running existing test cases (were you?) we have no way to report results (for instance if you were running Ubuntu Friendly test cases with checkbox, the tool reports your results for you, but I am not sure if it is available in other flavors than Ubuntu). If you were running our wiki test cases, results are reported on the tracker. Any problems you found you should raise a bug to make sure that someone fixes it. This is the most important part, in my opinion, especially if you were doing adhoc testing and not following any particular test case. Thanks, Gema > > > > ( Offical Asus support ... http://sourceforge.net/projects/eeecommunity/ ) > > Lubuntu Minimal (mini.iso)... > https://help.ubuntu.com/community/Lubuntu/Documentation/MinimalInstall > > > Cannot show console (can see flashing cursor pixels along top). > Wrong video mode. > > Lubuntu-Alternate ... > > Prerequisites > > > NOT DONE - Flash with latest BIOS - > http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+PC+4G%2fLinux&p=20&s=1 > > Testing > > > Keyboard detection cannot accept "ė" key (can't AltGr key?). > > - Solution ... pretend european "ė" keys are not there. Just > select "£" then it gets GB layout. > > - Result: Fully functional keyboard but NO European "ė" and other > special characters. > > - Other Eee specific keyboard functions work OK. > > > Memory after fresh install: 367 used, 132 free (out of 512. O swap. > Should be 50 - 60 used ? >Memory after optimisations below: 206 used, 281 free > > - Desktop Session Settings ... > > > Turning off ... SSH agent, Update Notifier, Cert & Key > Storage, Check for New Hardware Drivers, GPG Password Agent, Secret > Storage Service > > > removed /etc/xdg/autostart items ... bluetooth*, gnome*, > print*, update* > > - uneeded kernel modules ...add to /etc/modprobe.d/blacklist.conf > ... rfcomm (bluetooth), bluetooth, parpot_pc, ppdev, parport (parallel > port), joydev (gamepad/joystick), snd_rawmidi, snd_seq_midi, > snd_seq_midi_event, snd_seq_device ?, lp, at12 ?, bnep. > > - Don't use pcmanfm as desktop file manager ? > > - Remove xscreensaver ? used to blank screen. > > > Disk space 1.5 gig free > > > Optimisations (not tried yet) > > - Set noatime flag > > - EXT4 supports SSD - Set TRIM command support using the discard > mounting option in your fstab (or with tune2fs -o discard /dev/sdaX) - > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/filesystems/ext4.txt;h=10ec4639f1522dad34d66eea61443750435fe3ae;hb=HEAD > TRIM ... tested ? works? stable? > > > Cpufreq > >- "modprobe acpi-cpufreq" activates cpufreq system and puts > processor to 900mhz - or did "sudo apt-get install cpufrequtils" get > it working ? > >- unplugging power supply DOES NOT take cpu back to 633mhz. Seems > to be fixed > >- Jan 19 16:47:31 eeepc-lubuntu-djbarney kernel: [ 15.017494] > p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available > Jan 19 16:47:31 eeepc-lubuntu-djbarney dbus[461]: [system] Activating > service name='org.freedesktop.nm_dispatcher' (using servicehelper) > Jan 19 16:47:31 eeepc-lubuntu-djbarney dbus[461]: [system] > Successfully activated service 'org.freedesktop.nm_dispatcher' > Jan 19 16:47:32 eeepc-lubuntu-djbarney kernel: [ 15.808660] ondemand > governor failed, too long transition latency of HW, fallback to > performance governor > > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: QA wiki update
On 11/01/2012 17:49, Nicholas Skaggs wrote: > Alex, I started working through your version of the wiki also today. I > pulled some of the changes you had made and replaced/edited the relevant > sections on the main page. It would be good to get your content merged > asap, so it doesn't fall out of date. We have the ability to revert > changes, so I would encourage you to make your changes directly onto the > main site and we can tweak as we get more feedback. Thoughts? +1 It is quite confusing to have to send people to a temporary copy, having the new content on the main wiki would help loads keep improving. Plus, we have a very comprehensive new version already. > > Nicholas >> Hi Alex, >> thanks a lot for this change! My feedback follows. >> >> *Structure of the page* >> >> I think the wiki should have a clearer structure, so we should think >> about how to reorganize the text in a way that tells our story and >> sounds appealing to the reader. So I propose: >> >> == Welcome == >> > kinds of things does Ubuntu QA do?"> >> >> == What we do == >> > reworking> >> >> == Getting involved == >> > like a link to the qa-ubuntu list, qa launchpad group are good there, >> plus a link to our weekly meeting> >> >> == Currect Activities == >> >> >> == Contact Us == >> >> >> >> *Content of the page* >> >> - I think this statement needs rewriting: >> "The Ubuntu QA team is focused on developing tools, policies, and >> practices for ensuring Ubuntu's quality as a distribution as well as >> providing general advice, oversight, and leadership of QA activities >> within the Ubuntu project." >> >> AFAIK, we do not develop tools, we mainly use them. But we write and >> develop test cases :D >> >> - The areas in which QA is divided do not make much sense either, at >> least from my perspective, maybe it was like that in the past? Need some >> time to think about this one. >> >> - What is the difference between the "Testing Team" and the "QA Team"? >> We seem to have two different pages and I am not sure they are trying to >> convey different messages. The paragraph starting with "We cannot leave >> quality to good luck" is repeated in both. >> >> I love the design and the icons at the top, very stylish :D >> >> Cheers, >> Gema >> >> On 13/12/11 21:00, Alex Lourie wrote: >> >/ Hi all >> />/ >> />/ I've started working on our wiki [1] page update [2]. So far I've >> />/ cleared the obvious >> />/ parts (about Bug Squad for example), updated the content and >> changed the >> />/ order of things >> />/ to better cater to the potential reader. >> />/ >> />/ Please review and provide feedback :-) >> />/ >> />/ Thanks a lot. >> />/ >> />/ [1]https://wiki.ubuntu.com/QATeam >> />/ [2]https://wiki.ubuntu.com/AlexLourie/QAWikiNew >> />/ >> />/ -- />/ Alex Lourie >> />/ >> />/ >> / >> >> -- >> Gema Gomez-Solano> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa>> >> Ubuntu QA Teamhttps://launchpad.net/~gema.gomez >> <https://launchpad.net/%7Egema.gomez> >> Canonical Ltd.http://www.canonical.com >> >> > > > > > -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Meeting this week
Hi, so many things going on in this email, I think I am going to answer one by one. First an executive summary: I disagree with Alex and Javier perception of the importance of this issue at the moment (prioritization). Answers to Javier and Alex below. Gema On 09/01/2012 19:51, Javier Domingo wrote: > In my opinion, he is quite clear about the problem with ubuntu. For me for > example, its horrible to work with Ubuntu's Unity (for example), there are > lots of things that need to be much more tested, and with bugs they have > fixed. > I read the bug and it is a rant, no specifics about what is wrong nor pointers on how to reproduce, no nothing. In my opinion, this is a blog post, not a bug report. It is an opinion, not an objective problem with the system. > Its true that it is new, etc. But for example the gnome-core package comes > with a vino (VNC server) that is just crashing for one of the 5 (!!) > options it has due to a preference of the packager to not to use a miniupnp > lib included. And it has been included in last releases (at least). I know > Ubuntu is quite dependant on GNOME, but because GNOME changes > so drastically, quality of Ubuntu for changing to a new desktop enviroment > with not enought testing can't go so down. Ok, so maybe we need to add some automated testing to validate that gnome components are not broken on the latest versions. This has been added to our strategy and will be dealt with during next UDS. > What ubuntu did with the upgrade to unity, was to completely break with the > desktop in a very hard way. I think I have read enough about PERL 5 and 6 > and about Ubuntu and GNOME to compare this desktop environment upgrade. > We are doing daily testing and the Unity teams are also putting in place automated testing to correct this. Corrective measures are on their way and this is not our responsibility but a collective effort. > An example, would be as if now PERL guys decided to stop supporting Perl5 > and migrated everything with the actual state of things to Perl6. Though it > can be worked over Perl6, it is not enough for an environment where the > system can't have that many bugs. > > I don't really know if there has been a bug report increase, but I am > nearly sure that now bugs are more in general things than specific things > that just few people can bring up with them. Things like the one I reported > about vino server, included in the gnome-core (!!). > > That was my opinion, and though I don't know how to express it as I would > do in my native language, I think the idea is there. Thanks for your email, I think you expressed the ideas well and clearly. Take it from a fellow Spanish QA peer :) > > By the way, I am thinking seriously if we should be releasing so many > versions that fast, 6 months for a stable product if there are that big > changes, it is very difficult to be, This is out of question and out of our hands. We do not decide how often Ubuntu gets released nor we are going to be making this kind of decision in the future, the only thing we can try to influence is raising awareness of the quality of Ubuntu. So helping assess the quality of the product will help the release management team make informed decisions. In my experience, it is possible to release a version of an OS every 6 months, we used to do that with Symbian. The only thing you need is a very solid automated testing capability and good interoperability testing coverage (which in our case is achieved by manual community testing), so getting organized and working smoother together will help Ubuntu a great deal. > > Regards, > > Javier Domingo > (... I cut bits of the email that I don't think need answering ...) Alex's email: >>> >>> Hi Gema, and welcome back! >>> >>> I'm not sure that I'll make the meeting this week, so I only wanted to >>> raise one issue: there's a bug on launchpad, >>> https://bugs.launchpad.net/ubuntu/+bug/886931. >>> The person is complaining about the overall quality of Ubuntu (and >>> probably his specific own problems), but nevertheless, there's one point >>> that he raises that is quite important. I think that breaking commercial >>> software from working is a big problem for Ubuntu, and we should do >>> something about it. I agree with you that commercial software breaking is an issue, but I don't think that is only Ubuntu's fault. It is a shared responsibility, the commercial software vendors need to make sure their software works with Ubuntu too. Also, the user seems to behave quite recklessly, if you depend on some software for your work, you do not go and update to an intermediate version of Ubuntu that is not even guaranteed to be stable, you rely on LTSs and only upgrade to the next LTS. Also, you do not upgrade all your machines at once, you probably upgrade a non-critical one, make sure all the software you need to function works and then update the rest. So most of the problems he is complaining about are due to his own beha
Meeting this week
Hi all, thanks Phill for running the meeting last week! I am back from holidays so I can run the meeting on Wednesday. It'll be a short one, though, because we are in Budapest this week on the Precise Rally and we have a team dinner that night. I can give an update on what is being discussed and we can have an update from what is going on in the community and on the derivatives and spend only 30 mins on it. If anyone has anything pressing to discuss, please, bring it up at the beginning! Best Regards, Gema -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Next meeting chair
I am sure jibel can fix that when he is back from holidays. We have been trying to get the group more open to new members so that everyone participating in this list is part of it but didn't get to do it in the end. It's in the TODO list, though. Thanks, Gema On 28/12/11 12:14, Phill Whiteside wrote: > a request for membership has been filed, I was unaware it was a closed > group. Instead of asking via the meeting, can the Lubuntu-QA / testing > group be a sub group of Ubuntu-QA? > > Regards, > > Phill. > > On Wed, Dec 28, 2011 at 8:07 AM, Alex Lourie <mailto:djay...@gmail.com>> wrote: > > Hi Phil > > Just join the group and talk to jibel to approve you :-) > > > On Wed, Dec 28, 2011 at 10:01 AM, Phill Whiteside <mailto:phi...@ubuntu.com>> wrote: > > Oops, > > We have a possible problem. > > https://launchpad.net/~ubuntu-qa/+members#active > > > I'm not on there, just the mailing list :( > > Regards, > > Phill. > > > > > > > > > > On Tue, Dec 27, 2011 at 9:47 PM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > Thanks a lot for stepping in, Phill! I appreciate you > chairing if no one > else feels brave enough ;) > > This is due to my family trying to extend the holidays for a > couple of > days and me giving in :D I am sure we are all recharging > batteries to > find even more bugs when we return. > > Cheers, > Gema > > On 27/12/11 21:32, Phill Whiteside wrote: > > Hi Gema, > > > > I will, as previously promised, be chair if you cannot. > I'm hoping it is > > because of something like a family party and not an illness. > > > > I will await replies as to if I put my self forward. > Hopefully you will > > enjoy the minutes, the Lubuntu QA team has been created so > I am no > > longer alone :) > > > > hoping that you, everyone and their families are enjoying > the festive > > period Get you batteries re-charged as we charge, > headlong into an > > LTS :) From what I read, things are peaceful, this allows > us on QA to > > devote our limited resources to QA areas. > > > > Regards, > > > > Phill. > > > > On Tue, Dec 27, 2011 at 5:46 PM, Gema Gomez > > <mailto:gema.gomez-sol...@canonical.com> > > <mailto:gema.gomez-sol...@canonical.com > <mailto:gema.gomez-sol...@canonical.com>>> wrote: > > > > Dear all, > > > > I am likely to be unable to chair the meeting on the > 4th of January, if > > someone could do it for me, that'd be helpful. > > > > I hope you are all enjoying some time off. > > > > Thanks, > > Gema > > > > -- > > Gema Gomez-Solano > <mailto:gema.gomez-sol...@canonical.com> > > <mailto:gema.gomez-sol...@canonical.com > <mailto:gema.gomez-sol...@canonical.com>>> > > Ubuntu QA Team https://launchpad.net/~gema.gomez > > Canonical Ltd. http://www.canonical.com > > > > -- > > Ubuntu-qa mailing list > > Ubuntu-qa@lists.ubuntu.com > <mailto:Ubuntu-qa@lists.ubuntu.com> > <mailto:Ubuntu-qa@lists.ubuntu.com > <mailto:Ubuntu-qa@lists.ubuntu.com>> > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > > > > > > > > -- > > https://wiki.ubuntu.com/phillw > > > -- > Gema Gomez-Solano <mailto:gema.gomez-sol...@canonical.com>> > Ubuntu QA Team https://launchpad.net/~gem
Re: Next meeting chair
Thanks a lot for stepping in, Phill! I appreciate you chairing if no one else feels brave enough ;) This is due to my family trying to extend the holidays for a couple of days and me giving in :D I am sure we are all recharging batteries to find even more bugs when we return. Cheers, Gema On 27/12/11 21:32, Phill Whiteside wrote: > Hi Gema, > > I will, as previously promised, be chair if you cannot. I'm hoping it is > because of something like a family party and not an illness. > > I will await replies as to if I put my self forward. Hopefully you will > enjoy the minutes, the Lubuntu QA team has been created so I am no > longer alone :) > > hoping that you, everyone and their families are enjoying the festive > period Get you batteries re-charged as we charge, headlong into an > LTS :) From what I read, things are peaceful, this allows us on QA to > devote our limited resources to QA areas. > > Regards, > > Phill. > > On Tue, Dec 27, 2011 at 5:46 PM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > Dear all, > > I am likely to be unable to chair the meeting on the 4th of January, if > someone could do it for me, that'd be helpful. > > I hope you are all enjoying some time off. > > Thanks, > Gema > > -- > Gema Gomez-Solano <mailto:gema.gomez-sol...@canonical.com>> > Ubuntu QA Team https://launchpad.net/~gema.gomez > Canonical Ltd. http://www.canonical.com > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > > > -- > https://wiki.ubuntu.com/phillw -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Next meeting chair
Dear all, I am likely to be unable to chair the meeting on the 4th of January, if someone could do it for me, that'd be helpful. I hope you are all enjoying some time off. Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: U1 Smoke Tests
On 23/12/2011 10:31, Brendan Donegan wrote: > Hi, > > Testing a Precise daily today, I tried to log in to Ubuntu One, but came > across > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/908075 > > I use Ubuntu One to keep my SSH keys synchronized across systems, as > well as other useful bits and pieces for doing development (my .bashrc > and .vimrc for example). I therefore find it pretty essential that I can > use U1 on any install I make. > > I'd like to propose an Ubuntu One smoke test to be added to the smoke > tests being run on the daily images. Any objections? > > Thanks, > Sounds good to me, if we manage to deploy the test data correctly, which the tests we have don't do yet. This is supposed to be an automated test, right? Does this make sense for Desktop and Server or only Desktop? Thanks, Gema -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Meeting log - wk51
Hi everyone, thanks to everyone attending the meeting today: alourie, roignac, nuclearbob, ScottK, phillw and balloons. For those of you not able to make it, here is the log of the meeting: https://wiki.ubuntu.com/QATeam/Meetings/QA/20111221 Our next meeting will be the 4th of January 2012. We are skipping the meeting next week due to holidays. Further information available here: https://wiki.ubuntu.com/QATeam/Meetings Best Regards, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Test cases re-writing and classification
Hi Brendan, I think we could use the same doc, as discussed on the channel, maybe on a separate tab? Thanks, Gema On 21/12/11 11:38, Brendan Donegan wrote: > Hi Gema, > > I should probably remember this, but should we use the Google Doc for > new test cases (I've got some proper test cases for gnome-terminal in my > head)? > > Thanks, > > On 21/12/11 11:32, Gema Gomez wrote: >> Hi everyone, >> >> I have been doing some browsing of test cases in our wiki and found >> these ones: >> http://testcases.qa.ubuntu.com/Applications/Terminal >> >> I was trying to figure out how to classify the test cases when we get >> them into Case Conductor and realized, that in this case in particular, >> the test cases are wrongly classified. >> >> Take for instance, ter-001 test case, it says it affects gnome-terminal, >> and whilst I can see we are opening and closing the terminal, my >> impression is that test case is targeting sudo, apt-get, ls and bash, >> rather than the gnome-terminal. >> >> I think we need to start removing this kind of test case and adding >> tests that actually target the packages we are trying to test, so that >> if we decide to classify test cases based on the package they are >> testing, we have a clear view of those. Another alternative is to add >> all the affected packages to the list, not just the main one. I >> understand this was difficult with the current wiki, but in Case >> Conductor we will have more flexibility to assign test cases to more >> than one package. >> >> I hope you all have a nice holiday! >> Gema >> >> > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Test cases re-writing and classification
Hi everyone, I have been doing some browsing of test cases in our wiki and found these ones: http://testcases.qa.ubuntu.com/Applications/Terminal I was trying to figure out how to classify the test cases when we get them into Case Conductor and realized, that in this case in particular, the test cases are wrongly classified. Take for instance, ter-001 test case, it says it affects gnome-terminal, and whilst I can see we are opening and closing the terminal, my impression is that test case is targeting sudo, apt-get, ls and bash, rather than the gnome-terminal. I think we need to start removing this kind of test case and adding tests that actually target the packages we are trying to test, so that if we decide to classify test cases based on the package they are testing, we have a clear view of those. Another alternative is to add all the affected packages to the list, not just the main one. I understand this was difficult with the current wiki, but in Case Conductor we will have more flexibility to assign test cases to more than one package. I hope you all have a nice holiday! Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: A warm hello to everyone!
On 16/12/11 06:21, Alex Lourie wrote: > On Fri, Dec 16, 2011 at 6:57 AM, Nicholas <mailto:nska...@gmail.com>> wrote: > > Hello everyone. I wanted to introduce myself to you. My name is > Nicholas Skaggs -- yes, that guy Jono blogged about: > > http://www.jonobacon.org/2011/12/12/nicholas-skaggs-joining-the-canonical-community-team/. > I am excitied to be joining you in helping make ubuntu even better. > > I think ubuntu is in a unique place to be a leader among open source > projects in the area of QA. The more I have used ubuntu over the > years, the more impressed I become. Each release gets better and > better and provides a better experience. It's that "just works" > nirvana that all technology projects seek to provide its users and > ubuntu more and more "just works". I was reminded of this the other > day after coming home to find my wife happily printing some > documents using the new printer we had purchased. I hadn't yet had > time to setup the printer so imagine my surprise that my wife was > now printing from it! I asked her how she figured out how to setup > the printer and was met with a blank stare. She had simply turned it > on and plugged it in. Ubuntu did the rest when she hit the print > button -- ubuntu saw she wanted to print, found an > unconfigured printer available on USB, configured it, set it as the > default printer, and then sent the document to it. Amazing! It's > this community's tireless work and focus on finishing ideas well > that these experiences are a testament to. I look forward to > creating more and more of these experiences with all of you. > > I don't start in my new position with Canonical until next month, > but I will lurk on IRC, try to attend some meetings, and read the > list and wiki. Things seem to be standing up quickly around here so > I'll do my best to come up to speed on all the exciting things going > on. Thanks everyone! > > Nicholas > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > Hey Nicholas! > > Welcome to the team! We finally got to meet you, so we're glad and > anticipating to work with you! > > Let's make Ubuntu even better and more awesome than it is, and while > we're at it, let's bring open source QA to a new level. > > -- > Alex Lourie > > Hi Nicholas! Welcome to the team :) I hope we have the chance to start collaborating with you soon. We are in need of as many hands as we can get in the QA team :) We are working on some tasks at the moment, not sure when you joined the list, so this will give you an idea: https://wiki.ubuntu.com/QATeam/TasksPrecise We are making good progress in rewriting the test cases, reviewing the new tool we'll be installing (Case Conductor) and rewriting the wiki. Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Blueprints involvement
Hi all, I am thinking on adding alourie, kalosaurusrex, brendand and roignac to our blueprints as the people more involved for now in the work we are doing. This gives the work more visibility and makes your karma go higher as well as giving you the deserved credit for contributing to the Precise. I'd like to get more names involved, but I have not enough visibility to know what everyone is doing, so I will add (unless someone has any problem with it) your names to the tasks that are crystal clear to me for now. Let me know if you have any problem with this. Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Test cases review
Hi, I have reviewed the test cases we've generated so far and they look really good. I have added some comments, but I think they are an excellent starting point so far. Please, review them asap if you are planning to do it, so that we can mark them as reviewed and add the new versions back to the wiki! I'd say from now till Sunday we can spend reviewing, then after the end of this week we can update them and consider them done. https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&hl=en_US#gid=0 Thanks, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Meeting log - wk50
Dear all, thanks to everyone that attended the meeting today, great discussions ongoing. You can find the logs for the meeting here: https://wiki.ubuntu.com/QATeam/Meetings/QA/20111214 The Agenda for next week, unless someone wants to change it (in which case, by all means go for it): https://wiki.ubuntu.com/QATeam/Meetings Special thanks to all the people that attended today: alourie, roignac, brendand, besmirgogu, nuclearbob, phillw, jibel and kalosaurusrex Cheers, Gema -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Case Conductor requirements
Please, find below the requirements I will be discussing with them. I
have tried to ask for things that are going to benefit the tool as a
whole, other stuff like adding Open ID log-in I have been told we can do
easily internally.
Thanks for the excellent feedback everyone. Will keep you posted on the
outcome.
Gema
- Test case definition to have test case id (configurable format, see
below), test description (brief text field), assumptions (text field),
actions (text field) and expected results (text field shown next to
actions to facilitate the readability).
- Test case id: to follow some sort of pattern i.e. TC-COMP-{auto} where
{auto} would be a sequence auto-incremented and making sure no
collisions happen.
- Add status "Under Review" to test cases to facilitate test case life
cycle. It would be helpful if the status could be changed whilst editing
the test case as well, as one of the fields.
- Be able to link to a different bug repository than bugzilla. Making
the link configurable or so, because that would make our linking to
launchpad defects easy (our links look like this:
https://bugs.launchpad.net/ubuntu/+bug/899049).
- Add some kind of markup to be able to show bold, italics or
preformatted sections, we've found this bug[1] in your database that
suggests using html, but maybe some other markup language would be more
suitable (markdown, wiki syntax, etc).
- Are the permissions of the different roles configurable? If not, which
are the privileges of each of the roles?
- Adding the number of test cases per cycle would help the usability of
testcycles screen[2]
- Test cases management view could do with the date when each test case
was last modified.
- When a user is going to run a set of tests, it is currently difficult
to see which Product has runs available, maybe having a number between
brackets next to each one of them would help people find the right
places to run test cases.
I understand what you mean by Product and Runs, but what does Cycle
mean? If this is Mozilla specific terminology, could we make that
concept configurable?
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=667658
[2]: https://cc.oddsites.net/manage/testcycles/?openfinder=1
--
Gema Gomez-Solano
Ubuntu QA Team https://launchpad.net/~gema.gomez
Canonical Ltd. http://www.canonical.com
--
Ubuntu-qa mailing list
Ubuntu-qa@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: QA wiki update
Hi Alex, thanks a lot for this change! My feedback follows. *Structure of the page* I think the wiki should have a clearer structure, so we should think about how to reorganize the text in a way that tells our story and sounds appealing to the reader. So I propose: == Welcome == == What we do == == Getting involved == == Currect Activities == == Contact Us == *Content of the page* - I think this statement needs rewriting: "The Ubuntu QA team is focused on developing tools, policies, and practices for ensuring Ubuntu's quality as a distribution as well as providing general advice, oversight, and leadership of QA activities within the Ubuntu project." AFAIK, we do not develop tools, we mainly use them. But we write and develop test cases :D - The areas in which QA is divided do not make much sense either, at least from my perspective, maybe it was like that in the past? Need some time to think about this one. - What is the difference between the "Testing Team" and the "QA Team"? We seem to have two different pages and I am not sure they are trying to convey different messages. The paragraph starting with "We cannot leave quality to good luck" is repeated in both. I love the design and the icons at the top, very stylish :D Cheers, Gema On 13/12/11 21:00, Alex Lourie wrote: > Hi all > > I've started working on our wiki [1] page update [2]. So far I've > cleared the obvious > parts (about Bug Squad for example), updated the content and changed the > order of things > to better cater to the potential reader. > > Please review and provide feedback :-) > > Thanks a lot. > > [1] https://wiki.ubuntu.com/QATeam > [2] https://wiki.ubuntu.com/AlexLourie/QAWikiNew > > -- > Alex Lourie > > -- Gema Gomez-Solano Ubuntu QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Weekly meeting today
Dear all, we have our team meeting today at 17:00 UTC (in two hours roughly), in freenode channel #ubuntu-meeting. This has been a hectic and very productive week, I think. I hope to see you all there. The agenda and details for those of you who have never attended are available here: https://wiki.ubuntu.com/QATeam/Meetings Cheers, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Case Conductor requirements
Thank you all for the feedback, I am putting together the list to discuss with them. I will keep you posted in case you want to join the discussion, I still don't know which format it will be. Gema On 14/12/11 10:40, Vadim Rutkovsky wrote: > Hi guys, > > I've investigated CC a little and here are some info on our requirements: > - Test Case Definition >No separate field for Assumption section. I guess, we should add > this to Description > - Test Case ID >We may add this to testcase name and use as an ID > - Be able to have status for test cases (Draft/Under Review/Active/Inactive). > This is implemented. The only status missing is Under Review - > however, several users are required for this, so I could not try this > by myself. > - Be able to link with launchpad defects > Implemented > - Import testcases > Implemented, a bit buggy right now. A Gherkin-like format is used > > TODO: > - OpenID registration > - HTML in test description/steps > (https://bugzilla.mozilla.org/show_bug.cgi?id=667658) > - Export testcases (https://bugzilla.mozilla.org/show_bug.cgi?id=627785) > > > 2011/12/13 Alex Lourie : >> On Tue, Dec 13, 2011 at 8:15 AM, Vadim Rutkovsky wrote: >>> >>> I'd also like import/export functionality (in plain text, at least) >>> and some API for advanced reporting >>> >> >> +100! I forgot I wanted it too. >> >>> >>> 2011/12/13 Alex Lourie : >>>> How about test cases versioning? What is the test case needs fixing? >>> Agree with Alex, however we may cope with it using tags (e.g. >>> 'stable', 'for-review' etc.) >>> >> >> Interesting idea. While I'd prefer versioning, tags could work in absence of >> it. >> >>> >>> -- >>> Vadim Rutkovsky >> >> >> >> >> -- >> Alex Lourie > -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Case Conductor requirements
Hi QA team, I am not sure if you have all heard, but just in case. Litmus seems to be about to be substituted by a new tool the QA Mozilla team are developing. The new tool is called Case Conductor. https://wiki.mozilla.org/QA/TCM http://caseconductor.wordpress.com/ Since they are developing this tool now, about to finish though, but still under development, they have offered to consider our requirements for the tool. January is likely to be Beta testing time for Case Conductor. I have come up with these requirements so far: - Test Case definition for us is https://wiki.ubuntu.com/QATeam/TestCase (we need to be able to store test cases of that form in the tool). I already discussed this with them and didn't seem to be a problem. - Test case ID: The id need to be able to be something other than a number, ideally a predefined format of some sort. - Be able to have status for test cases (Draft/Under Review/Active/Inactive). Even though they have tags, I am not sure that is enough for tracking test cases. - Be able to link with launchpad defects In case any of you wants to start helping them: http://groups.google.com/group/case-conductor/browse_thread/thread/678a9213925a4d2f But I agreed with them that we'll be testing whenever their Beta is ready, they are re-engineering the UI at the moment and it seems a bit pointless to start testing the app before they finish this big change. If you have any other idea or requirement we could add to the list, please say so. I will check whether these things are covered already by the functionality in place or if they would be willing to add it. Thanks, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Gherkin DSL for testcase description and automation
Hi, I agree with Charlie, but I think it is worth discussing this idea and the reasons why (imo) this way of developing test cases wouldn't work in our case. When I was reading about this method in this thread it altogether reminded me of the days when we were trying to move the development of Symbian OS to agile methodology, we were asked to plan in a way that tasks had this format (also called stories in SCRUM): > As a I want so that (see http://www.thedailyscrum.co.uk/post/86171940/effective-story-writing-in-scrum) We underwent 2 years of intensive work trying to figure out how to do testing in such environment and trying to figure out how system testing, integration testing and unit testing fitted in this world. And believe you me, the Ubuntu dev world is much more complex than Symbian ever was. The first problem was that SCRUM doesn't really care about integration and system testing, it cares only about unit testing. The only reason I have been able to come up with for this is that SCRUM was initially developed for small projects where developers could talk to each other on daily basis plus the QA role wasn't a separate one. Only unit testing was required. I learned that for a big project this is not enough and you still need QA people and testers so that you get the integration of the product and the packaging of it right. But Agile was cool and we were forced to move to it. We did, and we implemented the lower layers of it, we wrote stories, tracked backlogs and did daily stand ups like champions. When it came to write test cases, ISTQB format still made sense for the whole company and was widely used. Even for unit testing we were using that when tests were written in something more formal than lines of code. The Gherkin method seems to be an evolution of Xtreme Programming or Agile (en.wikipedia.org/wiki/Behavior_Driven_Development). It is used for doing Behaviour Driven Development, i.e. the developer writes such test case, then implements the test code or generates it with a cucumber (I haven't figured out this bit but as funny as it sounds, it seems to be the way... a code generator from stories, call me old school, but I still prefer to write code with an editor) and then, when the test case fails, they go to the code and create the piece of software that will make that test case pass. That is unit testing, doesn't matter which language you use to write the test case. As we've seen with the example that roignac put together (thanks!), the language doesn't scale very well in terms of readability. Despite making the test case logically very accurate, it doesn't really make the manual tester's life easier, and at the end of the day, we are trying to attract people to do more manual testing. Irrespective of the subject having or not having a degree. It probably works for some programmers, but definitely doesn't work for testers (imho). In a diverse environment like ours where developers use different development life cycles (even though they all try to fit in the 6 month bound releases), I am not sure how we would be able to push this forward nor sure if we would want to do that if it is going to be more complicated than just getting the wording of the test cases right and accurate enough so that in front of the same behavior of the system, two different people fail the test in the same way (consistency). Those are my thoughts. More ideas? Thanks, Gema On 10/12/2011 14:43, Charlie Kravetz wrote: > On Sat, 10 Dec 2011 12:35:21 +0200 Руаньяк > wrote: > >> Hi, > >> 2011/12/10 Alex Lourie : >>> I have the following questions: >>> >>> 1. How long does it take to write something like that for >>> someone who's not a programmer and have no idea about Cucumber >>> or unit testing in general? >> I guess, it should not take much time. The only rule to be >> followed is 'Action after When, Expected result after Then, >> Concatenation is And'. Maybe, someone inexperienced in Gherkin >> could measure the time and post results here? For instance, this >> conversion of DesktopWhole case took about 10 min. for me. > > As someone completely ignorant of Gherkin, it took me over 10 > minutes to read through this test case. In reading through, I > attempted to picture most of the steps, and found the flow doesn't > work right here. I test a lot of images, and I test images daily. > This test is much too specific. Also, it does not read well, from > an english language user. It reads much like something written by > lawyers reads to the lay person. > > I don't think I could actually write such a test case, in less than > at least an hour, and perhaps that is not enough enough time. > > >>> 2. How would one execute this in LiveCD environment? >> Manual testers may use this as a usual test case. Whenever bug >> appears, the tester may break the instruction, e.g. --- When I >> double click 'Install Ubuntu' icon Then Ubuquity starts #here we >> can check main window etc. > >> Result: Ubiquity cr
Re: Gherkin DSL for testcase description and automation
+1 to brendand for putting it so clearly.
I am not very keen on rewriting everything twice, we should be creating
test cases that whether manual or automated, are reusable and not need
changing unless the behavior of Ubuntu changes. Otherwise, we are
shooting ourselves on the foot... we will always be catching up.
On the other hand, I am happy to do the intellectual exercise of trying
to imagine what a long test case would look like with Gherkin method,
and figure out if it would work. Can someone have a go at, let's say..
http://testcases.qa.ubuntu.com/Install/DesktopWhole
I think we need to ask ourselves at which level are we creating test
cases here. My take, is that we are trying to do system testing, because
we test on Alpha and Beta releases, and it is too late already for any
other kind of testing. So we are targeting Ubuntu as a whole, either
Desktop or Server. Our test cases should run on any architecture, though
(i386, AMD64, ARM Server whenever it comes along?).
I am happy to contribute to Alex's wiki about how to write test cases
whenever it is in place.
Gherkin.. worth considering, but it doesn't look very promising for the
problem at hand.
Thanks,
Gema
On 09/12/2011 13:51, Руаньяк wrote:
> Hi all,
>
> 2011/12/9 Alex Lourie :
>>
>>
>> On Fri, Dec 9, 2011 at 12:41 PM, Brendan Donegan
>> wrote:
>>>
>>> Not sure I buy some of the criticisms of the ISTQB definitions, but it's
>>> certainly true that Gherkin encodes the tests in such a way as to make
>>> it possible for tools to parse them, whereas perhaps ISTQB definitions
>>> don't have that. I do think the language ends up looking slightly weird
>>> for manual testers who may not have that much experience with the
>>> software though. Here's a weakness, at least in the definitions given
>>> below:
>>>
>>> Scenario: TC_CAL-002: Calculate sums
>>> Given Calculator is in Basic mode
>>> When I input "1+1"
>>>And I calculate result <- How?
>>> Then Result is "2" <- Where?
>>>And No error occurs <- Where does the error not occur?
> Yes, a poorly written scenario here. Anyway, these steps can be
> re-written in any possible way.
> The most important parts are keywords - Given, When, Then, And, But
> etc. - and step consistency (mostly for automation).
> We can even use bzr+launchpad to store testcases and Launchpad Code
> Merge for testcase review and merge. That would be great to
> find/develop a system, which will present the tests in Gherkin in cool
> sexy-looking way, which will be at the same time a) easy for manual
> testers, b) useful for automated testing team.
>
>>> I will concede that those things are probably rectifiable though. We
>>> just need to acknowledge that given a.) time and resource constraints
>>> and b.) the very nature of certain tests, we won't be able to automate
>>> everything and whereas ISTQB provides a definition which is probably
>>> easier to understand for the manual tester but not so much for tools,
>>> Gherkin DSL provides one that is easier for tools to understand but
>>> maybe vulnerable to providing definitions that are more difficult for
>>> manual testers.
>>>
>>
>> So, in fact, we kind of need to decide who should we cater more with the
>> test cases - manual
>> testers or automatic ones? I think we need to handle manual ones now, and
>> try to move as much
>> as possible for automation later. So ISTQB definition would get my +1 for
>> the nearest future.
> I guess, Gherkin tests are not that hard to understand and they have
> another feature - they are much easier to create new ones (simply as
> they use less symbols ;)
> If we use Gherkin DSL for both manual and automated tests, we will
> avoid converstion from manual tests to automated unit-test - and this
> takes a lot of time, as I've been developing some tests for Mago
> recently.
> Simply, automation team just have to write actions for each step, for
> instance:
> @Given('Calculator is in (.+) mode')
> def switch_to_mode(mode):
>
> @When('I click "(.+)" button')
> def click_button(button):
>
> etc. etc.
>
>>
>>>
>>> It also seems that it's background is unit test generation and I'd be
>>> curious to see what a larger test case written in this syntax would look
>>> like.
>>>
>>
>> And so would I :-)
> I havn't written many tests using Gherkin, here are some Mago tests
> rewritten - lp:~roignac/+junk/lettuce_experiment
> --
> Vadim Rutkovsky
>
--
Ubuntu-qa mailing list
Ubuntu-qa@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Test Cases categories
On 08/12/11 21:09, Alex Lourie wrote: > On Thu, Dec 8, 2011 at 7:57 PM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > On 08/12/11 15:06, Alex Lourie wrote: > > Hi all > > > > Proceeding with the work we started for test case rewriting, > there's an > > issue I'd like to discuss here - categorising the test cases. How > would > > we like it to be? What categories would you think should be > created? How > > do we decided the relation of a test case to a specific category? Can > > any given test be part of more than one categories? > > > > Please share your thoughts, > > Thanks. > > > > -- > > Alex Lourie > > > > > > The categorization we have at the moment is: > > - Applications > - System > - Hardware > - Install > - Upgrade > - CasesMods (not sure what this even means) > > There are many ways to categorize test cases: > > - by functionality under test (like we are sort of doing, but not quite) > > - by test type >* positive/negative >* smoke: target the system horizontally and superficially / > regression: > target vertical slices of the system, in depth >* Unit testing (target an api method, or a very small > functionality)/Integration testing (target the integration of two or > more subsystems)/System testing (target the system as a whole) >* Functional (target functionality, the system behaves as it > should and > fails gracefully in error situations) / Non-Functional (performance or > benchmarking, security testing, fuzzy testing, load or stress testing, > compatibility testing, MTBF testing, etc) > > - by test running frequency: this test case should run > daily/weekly/fortnightly/once per milestone > > > And many other ways. I am deliberately introducing a lot of jargon here, > for those less familiar with the QA speech, please have a look at the > glossary or ask when in doubt, if we want to truly improve the test > cases we are writing we need to start thinking about all these things: > https://wiki.ubuntu.com/QATeam/Glossary > > Thanks, > Gema > > > Hi Gema Hi Alex, > That's OK, we can handle the jargon. I think this is not true for everyone in the list, so I'd like to give everyone the opportunity not just to collaborate and add test cases but also to learn in the process. You may be comfortable with those terms but, some other people may not. > > I think that in our case, categories should represent our way of work. Categories should be related to the test cases and what they are trying to test, and they are something different from runlists or set of test cases that we run together. > So for community team, current categories are probably fine, but for QA > engineering they may not be well suited (you may want an additional > manual/automatic note). I think we should all be doing QA engineering. I don't see why the community work should be less accurate or valuable than the work done by QA engineering (who are these people anyway? you mean Canonical QA team?)... I think we are prepared to help whoever wants to do so, grow as QA engineers and learn, also respecting those that just want to spend some time running test cases and contributing in that way. Both are engineering tasks and valuable, they are just different. I don't believe community work has to mean lack of accuracy/quality or lack of engineering... apologies if I have misinterpreted your words, but I feel quite strongly about this. >I don't think we should stumble on this issue > for too long, so I'd recommend to go with the following scheme, and > update it if we feel necessary. Agreed, we shouldn't be stuck by this, just have it on the back of our minds and categorize test cases as we go along in a sensible way. We may find that in Precise our old categories are fine, but whenever the test suite grows we'll need to change that. And anybody writing test cases should feel empowered to add/remove categories if for whichever reason they don't make sense anymore or start making more sense. Also, we need to get people writing test cases thinking why they are doing that, what is the aim of a test case? is it to find problems? is it to demonstrate that a piece of functionality works? What is the pass criteria? Because otherwise we won't be writing good test cases that people can follow and report a result from. > So it would go as this: > > * *Applications* (for application related tests, such as testing > edit
Re: Test Cases categories
On 08/12/11 15:06, Alex Lourie wrote: > Hi all > > Proceeding with the work we started for test case rewriting, there's an > issue I'd like to discuss here - categorising the test cases. How would > we like it to be? What categories would you think should be created? How > do we decided the relation of a test case to a specific category? Can > any given test be part of more than one categories? > > Please share your thoughts, > Thanks. > > -- > Alex Lourie > > The categorization we have at the moment is: - Applications - System - Hardware - Install - Upgrade - CasesMods (not sure what this even means) There are many ways to categorize test cases: - by functionality under test (like we are sort of doing, but not quite) - by test type * positive/negative * smoke: target the system horizontally and superficially / regression: target vertical slices of the system, in depth * Unit testing (target an api method, or a very small functionality)/Integration testing (target the integration of two or more subsystems)/System testing (target the system as a whole) * Functional (target functionality, the system behaves as it should and fails gracefully in error situations) / Non-Functional (performance or benchmarking, security testing, fuzzy testing, load or stress testing, compatibility testing, MTBF testing, etc) - by test running frequency: this test case should run daily/weekly/fortnightly/once per milestone And many other ways. I am deliberately introducing a lot of jargon here, for those less familiar with the QA speech, please have a look at the glossary or ask when in doubt, if we want to truly improve the test cases we are writing we need to start thinking about all these things: https://wiki.ubuntu.com/QATeam/Glossary Thanks, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Test Cases Spreadsheet
On 08/12/11 12:31, Alex Lourie wrote: > On Thu, Dec 8, 2011 at 1:24 PM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > Dear all, > > after some debate in #ubuntu-testing this morning, we've created a > spreadsheet for everyone to share whilst we are working on the new test > case management system. > > Please, feel free to access it and start rewriting test cases: > > https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&authkey=CMTAtuoI&hl=en_US#gid=0 > > <https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&authkey=CMTAtuoI&hl=en_US#gid=0> > > Let us know if there is any problem. If you feel some column is missing > of something, fix it and let everyone know in the list. > > Whenever you are done with a test case and want comments on it, set the > Review Status to "FOR REVIEW", we can change it to "REVIEWED" once we > are happy with the test case. When you have a chunk of them for review, > send an email with the rows of the spreadsheet you want reviewed. We can > coordinate the comments in the list, I think. > > Thanks, > Gema > > -- > Gema Gomez-Solano <mailto:gema.gomez-sol...@canonical.com>> > QA Team https://launchpad.net/~gema.gomez > Canonical Ltd. http://www.canonical.com > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > > I have also created a notification trigger for myself, that would send > me daily digest of "Review Status" cells changes, so if someone requests > REVIEW I would know at the end of the day tops. > > -- > Alex Lourie Thanks Alex, let's aim at re-writing as many as we can and after they are reviewed we can put them back on the wiki substituting the old ones, so that new test cases can be used for Alpha 2 testing. Once the new test case management system is up and running, we'll write a script to import the test cases into it. It is easy to export a spreadsheet to almost any format we like. That way, if the new tool allows us to classify test cases by categories or similar, it is easier on the spreadsheet than by going through the wiki one by one. Thanks to everyone collaborating for this awesome start! Let's keep it up. Thanks, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Test Cases Spreadsheet
On 08/12/11 11:34, Brendan Donegan wrote: > On 08/12/11 11:24, Gema Gomez wrote: >> Dear all, >> >> after some debate in #ubuntu-testing this morning, we've created a >> spreadsheet for everyone to share whilst we are working on the new test >> case management system. >> >> Please, feel free to access it and start rewriting test cases: >> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&authkey=CMTAtuoI&hl=en_US#gid=0 >> >> Let us know if there is any problem. If you feel some column is missing >> of something, fix it and let everyone know in the list. >> >> Whenever you are done with a test case and want comments on it, set the >> Review Status to "FOR REVIEW", we can change it to "REVIEWED" once we >> are happy with the test case. When you have a chunk of them for review, >> send an email with the rows of the spreadsheet you want reviewed. We can >> coordinate the comments in the list, I think. >> >> Thanks, >> Gema >> > I just added 'Review Comments' and 'Reviewers Launchdpad ID' fields, as > these will be necessary for co-ordinating feedback > ok, Now I understood. I think we shouldn't be coordinating the reviews on the spreadsheet, but on the mailing list, because there may be many reviewers and it is complicated to do like that. Removing the launchpad id for the reviewer and leaving the Review comments one at the discretion of the author of the test case, in case they want to keep track of the comments there. We don't want to make this process ultracomplicated, just make sure we have reviewed things and the test cases look good. Thanks, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Test Cases Spreadsheet
On 08/12/11 11:34, Brendan Donegan wrote: > On 08/12/11 11:24, Gema Gomez wrote: >> Dear all, >> >> after some debate in #ubuntu-testing this morning, we've created a >> spreadsheet for everyone to share whilst we are working on the new test >> case management system. >> >> Please, feel free to access it and start rewriting test cases: >> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&authkey=CMTAtuoI&hl=en_US#gid=0 >> >> Let us know if there is any problem. If you feel some column is missing >> of something, fix it and let everyone know in the list. >> >> Whenever you are done with a test case and want comments on it, set the >> Review Status to "FOR REVIEW", we can change it to "REVIEWED" once we >> are happy with the test case. When you have a chunk of them for review, >> send an email with the rows of the spreadsheet you want reviewed. We can >> coordinate the comments in the list, I think. >> >> Thanks, >> Gema >> > I just added 'Review Comments' and 'Reviewers Launchdpad ID' fields, as > these will be necessary for co-ordinating feedback > I will remove that new "launchpad id" column and rename the "Author's email or launchpad id" launchpad id only. If someone doesn't have a launchpad id, please get one! Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Test Cases Spreadsheet
Dear all, after some debate in #ubuntu-testing this morning, we've created a spreadsheet for everyone to share whilst we are working on the new test case management system. Please, feel free to access it and start rewriting test cases: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AgtV30nnv18edFQzNVB4S2duOWNOT05zaHo3S0pNekE&authkey=CMTAtuoI&hl=en_US#gid=0 Let us know if there is any problem. If you feel some column is missing of something, fix it and let everyone know in the list. Whenever you are done with a test case and want comments on it, set the Review Status to "FOR REVIEW", we can change it to "REVIEWED" once we are happy with the test case. When you have a chunk of them for review, send an email with the rows of the spreadsheet you want reviewed. We can coordinate the comments in the list, I think. Thanks, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Meeting Log
Dear all, thanks to everyone that attended the meeting today, great discussions ongoing. You can find the logs for the meeting here: https://wiki.ubuntu.com/QATeam/Meetings/QA/20111207 The Agenda for next week, unless someone wants to change it (in which case, by all means go for it): https://wiki.ubuntu.com/QATeam/Meetings Special thanks to all the people that shared their thoughts today (since the chair doesn't participate, I think alourie gets the gold today): alourie (33) patrickmw (14) charlie-tca (12) kalosaurusrex (8) sconklin (8) brendand (7) nuclearbob (5) txomon (2) kamusin (2) roadmr (1) Cheers, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Meeting today
Just in case there's anyone with the same doubt: https://wiki.ubuntu.com/QATeam/Meetings The channel is #ubuntu-meeting Gema On 07/12/11 16:44, bilal khan wrote: > > in which channel? > On Wed, Dec 7, 2011 at 9:38 PM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > Dear all, > > we have a team meeting today at 5 UTC, which is in 20 mins. I > hope to see you all there! > > Cheers, > Gema > > -- > Gema Gomez-Solano <mailto:gema.gomez-sol...@canonical.com>> > QA Team https://launchpad.net/~gema.gomez > Canonical Ltd. http://www.canonical.com > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Meeting today
Dear all, we have a team meeting today at 5 UTC, which is in 20 mins. I hope to see you all there! Cheers, Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: QA tasks available
After reading through all the emails I have put together a little table that shows who is interested in what, so far only task 1 has been started. https://wiki.ubuntu.com/QATeam/TasksPrecise Thanks, Gema On 06/12/11 09:29, Brendan Donegan wrote: > On 05/12/11 16:24, Gema Gomez wrote: >> Dear QA Team, >> >> as promised, here it is a list of tasks that need to be done and we are >> in the process of doing that you could own if you have the time: >> >> - ISO testing tasks >> (https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing): >> >> >>1) Compile a list of applications that are installed by default by the >> ISO installers (one for Desktop, one for Server) and propose two or >> three basic test cases that could be run post install giving us basic >> confidence that the ISO is good for further testing (i.e. compile a list >> of post-install smoke tests that we could run with Jenkins). >> - This task is not about generating code, but about thinking of what >> packages of the ones installed are important and worth testing in a >> daily test suite. We could split it in different tasks for different >> people if we generate first a list of apps that we can use for the >> generation of test cases. > I'd like to start by encouraging some debate here. As a developer of > Ubuntu, there are certain tools that are critical such as Python itself. > However to what extent is it worthwhile testing that Python works for > example? I guess it can't do any harm. > > One thing I would like to see tested is apt - the ability to install > packages is critical. > > Personally I think the most important thing is to test as many different > configurations as possible (which we may already be doing), such as > encrypted home and selecting (or not) to install non-free > software/updates while installing. >>2) We need to fix the existing test cases in the tracker and convert >> them to a better, more understandable format. Basically we need to >> convert them to unambiguous and meaningful test cases. Some of them are >> redundant, some of them are too long to be just one test case, some >> others do not make sense anymore. This is a tidy up task that needs to >> be done. > Is this to be done before putting them into Litmus? I can gladly help > either way. >> >> - Metrics >> (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics): >>3) I have some tasks here that could use some help. We need to look at >> the codebase of Ubuntu main and see how to instrument the code so that >> we can start generating code coverage metrics. This is about compiling >> the Ubuntu code with gcov and generating binaries that can be used >> (still to be seen how to install them) for this end. >> - This task requires code in-depth knowledge and familiarity on how >> things are built and can be changed to build in a different way. We >> should decide where to start instrumenting and why. > The software-center developers have a very good implementation of code > coverage reports, so it's worth looking at that package (in the 'tests' > directory) at least for how to do this with a Python application. This > is the task I'd be most interested in helping with. >> >>4) Look into how to do test escape analysis with launchpad. TEA is an >> analysis that will tell us, after Precise, if we missed some problems >> that were found by someone after we did our testing and that should help >> us understand whether we should be adding new test cases in those >> "missed" areas or not. > Are we tagging bugs that 'we' found (I'm assuming the 'we' here means > the routine testing such as smoke testing and ISO testing rather than > regular use by end-users) in some way? >> >>5) Gather test cases from defects. This is about making a list of >> defects that have been fixed for Oneiric and that have a set of steps to >> reproduce the problem that needs to be gathered and written into a >> proper test case. > Does someone already have this list? Release managers for example? >> >> - Test Case Management System >> (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-management-tool) >> >> 6) Still not available, but when it is, review and give feedback >> about litmus and its usability. Also help decide how to configure it to >> make it more suitable for the Ubuntu community testing. > Just let us know when it's ready ;) >> >> >> - QA Backlog tasks >> (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-backlog)
Re: ISO manifest inconsistent with installed packages
On 06/12/11 19:21, Aaron wrote: > Well I'm happy to report that the installed applications from the LiveCD > do indeed match the application manifest! > > Sorry about that. Nothing to be sorry about! I didn't know that either, so assumed that the manifest was the right place to look. So we should probably look at the packages that are installed on an imaged installed by default, in the default language (i.e. English) without Internet connection. Good work, thanks for looking into this! Gema > > A > > On Tue, Dec 6, 2011 at 7:57 AM, Aaron <mailto:aa...@browncoat.us>> wrote: > > I did not select to install any updates or third party applications, > but I'm going to check this again on a LiveCD and see how the > differences look. > > Thanks for your time! > > Aaron > > > On Tue, Dec 6, 2011 at 12:55 AM, Jean-Baptiste Lallement > mailto:jean-bapti...@ubuntu.com>> wrote: > > On 12/06/2011 01:45 AM, Aaron wrote: > > I am looking at how consistent the ISO manifest is with the > actually > installed packages in Precise. The basic steps I did are: > > 1. Download ISO from > http://cdimage.ubuntu.com/__daily-live/current/ > <http://cdimage.ubuntu.com/daily-live/current/> > (download with date stamp for today) I did a install (not > live cd) in > VirtualBox. > > 2. Download the manifest for the ISO (for i386 below is the > path) > (download with date stamp for today) > > wget > > http://cdimage.ubuntu.com/__daily-live/current/precise-__desktop-i386.manifest > > <http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.manifest> > > Just to clear a confusion here, the manifest on cdimage.u.c > lists the contents of the live filesystem, not the installed > filesystem. > > Content of the live filesystem and a freshly installed system > are different because, some packages on the Live CD are only > useful to the Live CD and the installer, only the language (and > langpacks) the user selects is installed, additional software > can be installed (in your case virtualbox packages, but also > flashplugin, codecs, updates, additional langpacks not on the > CD, i386 packages due to multiarch support if you're installing > on amd64 and need i386 libs, ...) > > > -- > Jean-Baptiste > irc: jibel > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/__mailman/listinfo/ubuntu-qa > <https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa> > > > > > -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: ISO manifest inconsistent with installed packages
Aaron, did you choose to update during install and install third party
software? Any of those two?
Gema
On 06/12/11 08:32, Brendan Donegan wrote:
> It won't be consistent, because you'll make some choices during
> installation that will affect which packages are actually installed. Not
> everything on the CD ends up in the installation of Ubuntu.
>
> On 06/12/11 00:45, Aaron wrote:
>> I am looking at how consistent the ISO manifest is with the actually
>> installed packages in Precise. The basic steps I did are:
>>
>> 1. Download ISO from http://cdimage.ubuntu.com/daily-live/current/
>> (download with date stamp for today) I did a install (not live cd) in
>> VirtualBox.
>>
>> 2. Download the manifest for the ISO (for i386 below is the path)
>> (download with date stamp for today)
>>
>> wget
>> http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.manifest
>>
>> 3. Create installed package list:
>>
>> dpkg -l > dpkgl.txt
>>
>> 4. Strip out the Name and Version columns to separate file:
>>
>> awk '{print $2 , $3}' dpkgl.txt > dpkg-name-version.txt
>>
>> Diff the manifest and the current installed packages (with only the
>> name/version columns):
>>
>> diff --ignore-space-change precise-desktop-i386.manifest
>> dpkg-name-version.txt > diff2.txt
>>
>> All output from my process attached. But here is the diff2.txt (below
>> and attached)
>>
>> It seems like the manifest is not reflecting 100% what is installed,
>> unless I am missing something?
>>
>> Thoughts?
>>
>> First file is the 'precise-desktop-i386.manifest' and the second file
>> is the 'dpkg-name-version.txt' (which is the currently installed
>> packages via dpkg).
>>
--
Gema Gomez-Solano
QA Team https://launchpad.net/~gema.gomez
Canonical Ltd. http://www.canonical.com
--
Ubuntu-qa mailing list
Ubuntu-qa@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: QA tasks available
Hi Aaron, On 05/12/11 19:59, Aaron wrote: > I'd be interested in starting on ISO Testing and task 1. I think it > would give me some good initial exposure to the overall > picture--installed applications, some testing priority and making some > ISO smoke test--test cases. If that sounds okay? thanks, that is excellent! > Is there a notification for when packages with changes are submitted to > the code base? Or some other process for knowing what packages have been > added and changed? Has there been any initial discussions on testing > priority? I'm sure I can come up with an initial list and we can start > from there if not. The place where I would start is the manifest (imagename.manifest file) for the images, that tells you what is in the CD: http://cdimage.ubuntu.com/daily-live/current/ This will tell you the list of packages in a particular image and then, you need to come up with some test cases for the important bits of the image. This is meant to be smoke testing, so only positive test cases are recommended, with some default options, if we can run them from command like they are easily automatable. > I'd be interested in having a clear picture of what has changed between > builds/releases and help determine what should be included in the smoke > testing, etc. This we'll have to figure out and discuss, the main users of the daily images are: - Developers: they need to work on the latest software to be able to compile, so basic dev tools need to be fully functional - Testers/QA: people that need to perform further testing on the images. So they need the basics working, editing of files, file system, basic admin tools, etc. > > Getting a list of the packages isn't hard so I was thinking about how to > determine testing priority and making the test cases, etc. We have to come up with the criteria. > Unless someone is already on it or if you'd like me to look at something > else instead... It's all yours, if someone else wants to help, they can coordinate with you on it :) Let's try to get the criteria/priorities right and then maybe more people can help when we are clear on what needs testing. > > Thanks! > *Thank you!* Please, start a new thread when you have something to share/questions/anything for review and we can all collaborate/give you feedback there. Gema > Aaron > > On Mon, Dec 5, 2011 at 8:24 AM, Gema Gomez > <mailto:gema.gomez-sol...@canonical.com>> wrote: > > Dear QA Team, > > as promised, here it is a list of tasks that need to be done and we are > in the process of doing that you could own if you have the time: > > - ISO testing tasks > > (https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing): > > 1) Compile a list of applications that are installed by default by the > ISO installers (one for Desktop, one for Server) and propose two or > three basic test cases that could be run post install giving us basic > confidence that the ISO is good for further testing (i.e. compile a list > of post-install smoke tests that we could run with Jenkins). >- This task is not about generating code, but about thinking > of what > packages of the ones installed are important and worth testing in a > daily test suite. We could split it in different tasks for different > people if we generate first a list of apps that we can use for the > generation of test cases. > 2) We need to fix the existing test cases in the tracker and convert > them to a better, more understandable format. Basically we need to > convert them to unambiguous and meaningful test cases. Some of them are > redundant, some of them are too long to be just one test case, some > others do not make sense anymore. This is a tidy up task that needs to > be done. > > - Metrics > (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics): > 3) I have some tasks here that could use some help. We need to look at > the codebase of Ubuntu main and see how to instrument the code so that > we can start generating code coverage metrics. This is about compiling > the Ubuntu code with gcov and generating binaries that can be used > (still to be seen how to install them) for this end. >- This task requires code in-depth knowledge and familiarity > on how > things are built and can be changed to build in a different way. We > should decide where to start instrumenting and why. > > 4) Look into how to do test escape analysis with launchpad. TEA is an > analysis that will tell us, after Precise, if we missed some problems > that were found by someone after we did our testing and that s
QA tasks available
Dear QA Team, as promised, here it is a list of tasks that need to be done and we are in the process of doing that you could own if you have the time: - ISO testing tasks (https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing): 1) Compile a list of applications that are installed by default by the ISO installers (one for Desktop, one for Server) and propose two or three basic test cases that could be run post install giving us basic confidence that the ISO is good for further testing (i.e. compile a list of post-install smoke tests that we could run with Jenkins). - This task is not about generating code, but about thinking of what packages of the ones installed are important and worth testing in a daily test suite. We could split it in different tasks for different people if we generate first a list of apps that we can use for the generation of test cases. 2) We need to fix the existing test cases in the tracker and convert them to a better, more understandable format. Basically we need to convert them to unambiguous and meaningful test cases. Some of them are redundant, some of them are too long to be just one test case, some others do not make sense anymore. This is a tidy up task that needs to be done. - Metrics (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics): 3) I have some tasks here that could use some help. We need to look at the codebase of Ubuntu main and see how to instrument the code so that we can start generating code coverage metrics. This is about compiling the Ubuntu code with gcov and generating binaries that can be used (still to be seen how to install them) for this end. - This task requires code in-depth knowledge and familiarity on how things are built and can be changed to build in a different way. We should decide where to start instrumenting and why. 4) Look into how to do test escape analysis with launchpad. TEA is an analysis that will tell us, after Precise, if we missed some problems that were found by someone after we did our testing and that should help us understand whether we should be adding new test cases in those "missed" areas or not. 5) Gather test cases from defects. This is about making a list of defects that have been fixed for Oneiric and that have a set of steps to reproduce the problem that needs to be gathered and written into a proper test case. - Test Case Management System (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-management-tool) 6) Still not available, but when it is, review and give feedback about litmus and its usability. Also help decide how to configure it to make it more suitable for the Ubuntu community testing. - QA Backlog tasks (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-backlog) 7) Review and change the wiki to reflect the new approach to QA. Please, bear in mind that since we don't have the test case management tool up and running yet, we need to keep our test cases in text files or open office documents (prefereably spreadsheets) for now. As soon as we have chosen a tool to handle them, we will be using that. I have added a template at the bottom of the test cases page, feel free to use it for your newly generated test cases: https://wiki.ubuntu.com/QATeam/TestCase You can also modify it to contain a link to the old test case whenever you are improving an existing test case. Let us know which tasks you are interested in and I will be mapping tasks in the blueprints to people, so that we keep track of what everyone's doing and do not duplicate work. I have numbered the tasks to make it easier to discuss about them. You don't need to take an entire task if you feel you can only work on two or three test cases, you just say so and we will make sure nobody else is working on the same ones as you. Looking forward to your answers! Gema -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Hello!!
Hi Besi, welcome to the ubuntu QA team! Looking forward to collaborating with you :D Gema On 01/12/11 13:17, Besmir Gogu wrote: > Hello Everyone, > > My name is Besi and I am from Albania. I joined a couple of weeks ago > but failed to introduce myself. > I am a computer science specialist working in the mobile telecom industry. > I would like to get involved more with the Ubuntu projects as I believe > that you are doing an amazing work here. > I have chosen Ubuntu as a linux distro and I believe that I can learn so > much more by getting involved. > I do not have a lot of experience in Ubuntu itself although I believe > that given the chance I can learn and do much. > > Thank You > Besi > > -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Starting once more
Hi Javier, thanks for your email. Nice to see other fellow Spanish collaborator in the list (apart from the ones I already knew :)! Regarding the blueprints, we normally put them together before UDS and discuss them there. For those of you who weren't there, this is the overall strategy we presented for the coming two years. It is only very clear for the next six months and we will be defining together the coming cycles as we get closer and see what we have achieved: https://wiki.ubuntu.com/QATeam/AutomatedTesting/Strategy As per the definition of test case, that is my mistake, I should have pointed to the exact same public page in the wiki (I will change that in the blueprint): https://wiki.ubuntu.com/QATeam/TestCase As you can see the blueprints more or less match what is explained in the strategy, some of them have tasks that we also need to do due to the lab requiring updates, etc. that are not necessarily there. This cycle is all about enabling the developers and engineering teams do their job better. Next one will be about adding more test cases (increasing the coverage) to our test suites. As I said, I will try to put a list of tasks together for Monday, where people can choose the ones they like from the ones we have available and are doing in those blueprints. Things keep coming up and we keep adding more things to the blueprints as we go along. One thing you could do is express your interest in one blueprint or another and we can match tasks with people's levels of expertise or get the people with less experience to collaborate with the more experienced ones. We can also look into the minimal CDs testing if you want, but at the moment we are going to focus on getting right the ISOs we have available, before expanding into new things. More info to come soon, Gema On 01/12/11 07:45, Javier Domingo wrote: > Hi all, > > First of all, I want to say that I have been reading all the mails you > have regularly sent, and I want to say I'm glad that there are going to > happen big changes. > > Refering to those changes, thought I have not been quite active this > year, I am particularly interested on minimal CD installations. I think > they are the best way to install OS for people that already knows they > want it, and they don't want to install it and then update it [1]. In > this way, I would like to see those Minimal CDs into the iso tracker. I > don't know actually why they are not there. > > What involves the test-case definition blueprint, I am not allowed to > see the canonical wiki (don't know if this is actually pretended). And > it would be nice an explanation of what blueprints, etc. are. I actually > pretend to do more than just testing, I have no idea of how are things > organized, which teams there are, etc. > > Greetings, > > Javier Domingo > > > [1] I would like to say that I random times experienced problems when > installing from minimal CDs. Those times were when I used my spain's (my > country) archive copy. I don't know if there might not be any > difference, but after selecting the archive, it gets stuck randomly.I > would like to have more facilities at install time to know what is > happening (any debug info or sth). Would be perfect a debugging flag at > boot time or something. > > > > -- Gema Gomez-Solano QA Team https://launchpad.net/~gema.gomez Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: well, here's my hello as well
Hi Aaron, welcome to QA! It's very valuable for us the experience you show in your CV, I am sure you'll find interesting the challenges we are facing when trying to make the most of the testing we are doing. You could, not only contribute yourself but also help others get up to speed with the QA concepts and basics. Since there is many of you guys who have expressed the will to help in new things, I will put together a list of tasks that are in progress or about to start that you all may find interesting and send it to the list to see if there are any takers. I work mainly for the Ubuntu projects, maybe the guys from other distros that are also in the list can do the same, so that we have a good pool of things for new starters to have a go at. I am off for a long weekend starting tomorrow so I will probably send ours on Monday or so. Thanks, Gema On 01/12/11 01:19, Aaron wrote: > I've been on the list for awhile but haven't been very active in the > community for a year or so. > > I was on the HP Linux Imaging and Printing project for 5 years doing QA > and Technical Support. > > I would like to now find a project or area of focus so that I can > continue to be active in the community. > > If there is an area or team that would have me, I'd love to help with > the next release. > > Here is my linkedin profile for more of my background: > > http://www.linkedin.com/in/albrigha > > Ideally I'm looking for a specific project to be assigned that I can > help with. > > So please feel free to be in touch on how I can participate! > > Thanks for your time! > > Aaron > > -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Hello everyone
Hi, welcome to the ubuntu QA team! We'll see if we can find some specific tasks that will help you with your goals :) Gema On 30/11/11 22:11, Phill Whiteside wrote: > Hi Peter, > > Welcome to QA. > > if you can, please do attend some / any / all weekly meetings, details > are at https://wiki.ubuntu.com/QATeam/Meetings > > <https://wiki.ubuntu.com/QATeam/Meetings>that section also includes the > minutes from meetings so you can keep up to speed on what is being > discussed. Other than that, please feel free to ask any questions on the > mailing list. > > Regards, > > Phill. > > <https://wiki.ubuntu.com/QATeam/Meetings> > > On Wed, Nov 30, 2011 at 8:11 PM, Kristijan <mailto:kiki.tka...@gmail.com>> wrote: > > Welcome Peter. > > > 2011/11/30 krecikos87 <mailto:kreciko...@gmail.com>> > > Hello, > > I am Peter and I had joined Ubuntu QA community few days ago. > > I am a electronic engineer with 1 year experience in software > testing. > > I have three reasons joining Ubuntu QA team: > 1. I would like to improve system to be sure that I am using really > stable and easy going operating system. > 2. I would like to get experience in using Linux system. > 3. Increase my knowledge in software testing. > > Looking forward to participate, > Best regards, > Peter > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > > > -- > Kristijan Tkalec > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com <mailto:Ubuntu-qa@lists.ubuntu.com> > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > > > -- > https://wiki.ubuntu.com/phillw > > -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: New QA Meeting, today at 17:00 UTC
On 30/11/11 15:02, Gema Gomez wrote: > Dear all, > > we will be having our new QA Team Meeting today at 17:00 UTC, right > before the Bugs Meeting in #ubuntu-meeting. > > Today we will be discussing the new format of the meeting and we will > give an update of all the blueprints we are working on at the moment in > the QA Team. > > Find the temporary agenda in the usual place: > https://wiki.ubuntu.com/QATeam/Meetings > > Any questions/concerns/ideas please bring them to the meeting and let's > discuss them. > > See you there, > Gema > > > The meeting happened at the agreed time. Big thanks to everyone that attended. There was conversation around how to get people collaborating with automated testing, we will keep you all posted on the progress. For those of you who are developers as well as testers, there will be plenty of opportunity to contribute test code. Meeting logs: https://wiki.ubuntu.com/QATeam/Meetings/QA/2030 Thanks, Gema -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: New QA Meeting, today at 17:00 UTC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/11/11 15:33, Charlie Kravetz wrote: > On Wed, 30 Nov 2011 15:29:35 +0000 Gema Gomez > wrote: > >> On 30/11/11 15:11, Charlie Kravetz wrote: >>> On Wed, 30 Nov 2011 15:02:36 + Gema Gomez >>> wrote: >>> >>>> Dear all, >>> >>>> we will be having our new QA Team Meeting today at 17:00 UTC, >>>> right before the Bugs Meeting in #ubuntu-meeting. >>> >>>> Today we will be discussing the new format of the meeting >>>> and we will give an update of all the blueprints we are >>>> working on at the moment in the QA Team. >>> >>>> Find the temporary agenda in the usual place: >>>> https://wiki.ubuntu.com/QATeam/Meetings >>> >>>> Any questions/concerns/ideas please bring them to the >>>> meeting and let's discuss them. >>> >>>> See you there, Gema >>> >>> >>> >>> >>> I do not like this new meeting thing. For me, as a derivative >>> QA, it now costs me two hours for the QA meeting, since I am >>> all of QA for Xubuntu. We don't have two people, nor do we >>> really have a need for two people. >>> > >> Thanks for bringing this up, Charlie. You are one of the few >> people that were present in most meetings, and as you know, we >> didn't have a lot of outside presence in them. This, and the >> changes that are undergoing in QA, that require more focus, are >> the reasons why we are changing the format of the meetings. >> Maybe, by bringing the right attention to QA and the right >> attention to bugs, we can increase the QA community and find >> someone that can help you as well. > >> We are going to document and publish everything that is >> discussed in both meetings, so anyone could make use of the >> mailing lists to discuss any concern if they are not able to >> attend one of the meetings in person. > >> Historically, in Ubuntu, bug triaging and QA have been very >> interconnected and often confused, by bringing that separation >> to it we are increasing our chances of success in doing better >> testing and better triaging, in my opinion. We'll help you with >> you time problem if you cannot attend some of the meetings, and >> we will consider compressing both meetings to 30 mins each if >> that is all the time that is required, let's see how it goes and >> how much time is really necessary for each once they are >> established in their new formats. > >> Thanks, Gema > > Thank you. I don't the length of the meeting matters so much, if I > have to plan to be in #ubuntu-meeting at both 17:00 and 18:00 > UTC. That takes a big chunk out of day. > Yep, I agree, if things go smooth and the time required for the QA meeting, for instance, is 30 mins, we could start at 17:30. Or if that is the case with the bugs meeting as well, we could schedule both within the same hour (either 1700 or 1800). It is just arbitrary to assign an hour to the meetings, since we don't know how long they are going to end up being, they could be 30 mins each and occupy only one hour in total. Let's see how it goes and then rearrange the schedule accordingly. Let's give ourselves a couple of weeks to settle the new agendas and we could have by January a definitive schedule that suits everyone. - -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO1k3jAAoJEGrsYwHIaYlg0J0H/2I1sY14MSDsNewl4XOmuxYb dlD08seJLNlIPKJnTKqYUhbEOVigS3Il1LioyLwP0dkmCPG6wA++QIGC8otdmONo LsGb8jSueUpd9xCe3CKsRkRAULsSXEOzPDEWWvuy80YnDO5JnhUv0O3u8+6Vsp1M 51D4PUYCq8dRkg5Z9KjIE7+MsY9cJs2CaqaUdvcyF5SxNDEPRJuj2XLKcXJKRfyM hq66QWzzwCJ+n2gLNddolH+1ZlCMTtBxYXV4BF59S1DN+URSrwRZ641/CqUbz1f4 I88FjsShSze6BSGrshoF70rUWn+nA3Uh48biS7MlLacki2iOzBzebReN1ak4BE0= =+b0t -END PGP SIGNATURE- -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: New QA Meeting, today at 17:00 UTC
On 30/11/11 15:11, Charlie Kravetz wrote: > On Wed, 30 Nov 2011 15:02:36 +0000 Gema Gomez > wrote: > >> Dear all, > >> we will be having our new QA Team Meeting today at 17:00 UTC, >> right before the Bugs Meeting in #ubuntu-meeting. > >> Today we will be discussing the new format of the meeting and we >> will give an update of all the blueprints we are working on at >> the moment in the QA Team. > >> Find the temporary agenda in the usual place: >> https://wiki.ubuntu.com/QATeam/Meetings > >> Any questions/concerns/ideas please bring them to the meeting and >> let's discuss them. > >> See you there, Gema > > > > > I do not like this new meeting thing. For me, as a derivative QA, > it now costs me two hours for the QA meeting, since I am all of QA > for Xubuntu. We don't have two people, nor do we really have a need > for two people. > Thanks for bringing this up, Charlie. You are one of the few people that were present in most meetings, and as you know, we didn't have a lot of outside presence in them. This, and the changes that are undergoing in QA, that require more focus, are the reasons why we are changing the format of the meetings. Maybe, by bringing the right attention to QA and the right attention to bugs, we can increase the QA community and find someone that can help you as well. We are going to document and publish everything that is discussed in both meetings, so anyone could make use of the mailing lists to discuss any concern if they are not able to attend one of the meetings in person. Historically, in Ubuntu, bug triaging and QA have been very interconnected and often confused, by bringing that separation to it we are increasing our chances of success in doing better testing and better triaging, in my opinion. We'll help you with you time problem if you cannot attend some of the meetings, and we will consider compressing both meetings to 30 mins each if that is all the time that is required, let's see how it goes and how much time is really necessary for each once they are established in their new formats. Thanks, Gema -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
New QA Meeting, today at 17:00 UTC
Dear all, we will be having our new QA Team Meeting today at 17:00 UTC, right before the Bugs Meeting in #ubuntu-meeting. Today we will be discussing the new format of the meeting and we will give an update of all the blueprints we are working on at the moment in the QA Team. Find the temporary agenda in the usual place: https://wiki.ubuntu.com/QATeam/Meetings Any questions/concerns/ideas please bring them to the meeting and let's discuss them. See you there, Gema -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Introductory email
Hi all, I have just realized I sent yesterday's email without having introduced myself to the ubuntu-qa team, my bad. I am a QA Engineer and in August I joined the QA Platform Team at Canonical. I love being part of this initiative to improve the quality of Ubuntu and I am looking forward to collaborating with all of you. Regarding my experience as QA Engineer, I worked for years at Symbian/Nokia first as a Test Integration Engineer, later as a System Test Engineer. Later I worked for VMware also as QA Automation Engineer. My main aim at those companies has been test automation, which I am passionate about (but only when it makes sense, automation is very expensive!). You can have a look at the QA Team strategy here: https://wiki.ubuntu.com/QATeam/AutomatedTesting/Strategy During this cycle we are going to be making ISOs stable and reliable so that further and more rewarding testing is possible during the whole cycle. We are also piloting a tool called litmus, for test case management, we'll let you know when it is ready to be used. We'll also be putting together some metrics so that we can measure how good is our automated testing going forward and so that we can add test cases where they are needed the most. If you like testing and you are a programmer, you may want to get in touch with us. If you have a bunch of test cases you think are good and help you find plenty of defects each cycle, you can send them to the list and we can discuss whether it is worth automating them and how to proceed. We have established a definition of test case that we should all use from now on when writing test cases (either automated or manual): https://wiki.ubuntu.com/QATeam/TestCase Any questions please send them here so that we can all learn from them. Best Regards, Gema -- Gema Gomez-Solano QA Team +44 799 053 7303 Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
QA Team Meeting and Bugs Meeting split from next week
Dear all, in an attempt to get more involvement from the community in *bug analysis and triaging* and *quality assurance and testing*, the BugSquad and QA Platform Teams have decided to split the Wed 18:00 GMT Ubuntu QA Team Meeting in two separate meetings with separate objectives. Since we are going to be putting a lot of effort this cycle into ensuring testing and bug triaging are done better and we are going to be contributing in different ways to improving the quality of Ubuntu, we've decided to schedule two meetings so that people interested in bug triaging do not need to hear all about the testing and vice versa. Having said that, we are aware that some contributors are interested in the two areas, so we've scheduled the new QA Team meeting one hour earlier than the Bug Squad meeting, so that if someone wishes so, they can attend both without too much disruption. Please, for further information keep an eye on: * https://wiki.ubuntu.com/QATeam/Meetings - Wed 17:00 GMT *Focus*: QA platform activities, calls for testing, community feedback, etc. *Who should attend*: Anyone interested in contributing doing testing for Ubuntu is welcome to attend and start sharing their views, contributing. We'll make sure all the efforts count towards the quality of the coming release. * https://wiki.ubuntu.com/BugSquad/Meetings - Wed 18:00 GMT *Focus*: Bug triaging, mentoring of new members, ongoing activities discussion, etc. *Who should attend*: Anyone interested in bug triaging, bug management, bug metrics and classification of bugs. Next week we will be discussing the new agendas and agreeing on a new format that makes sense. Pedro will be chairing the Bugs meeting and I will be chairing the QA Team meeting, we hope we see you all there! The Ubuntu Fridge Calendar, already has the schedule information of the meetings from next week onwards: http://fridge.ubuntu.com/calendars/fridge/ Best Regards, Gema -- Gema Gomez-Solano QA Team Canonical Ltd. http://www.canonical.com -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
