Re: QA tasks available
I'd be interested in helping with the test case cleanup and smoke test brainstorming (tasks 1 and 2). -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re:
On Mon, Apr 11, 2011 at 13:35, Alexander Vinbæk Strand alexstra...@gmail.com wrote: Does someone knows when the 11.04 release is? And is 11.04 more stable than 10.10, because 10.10 is hanging when I login to my desktop every second time I logged in! it's in April 2011 ;-) specifically 28 April 2011. As for stability, who knows... it depends a lot on hardware... it's better on some systems than others. It seems to run fine on the two Lenovo systems I have it on, but YMMV. -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: ISO testing: reporting bugs on current versions
On Mon, Jun 7, 2010 at 13:23, Brian Murray br...@ubuntu.com wrote: On Mon, Jun 07, 2010 at 09:17:53AM -0400, J wrote: I usually put the release in the Bug subject line, something like this: [Maverick A1]Something happened that was bad and this broke. It'd be best if you did not use the bug's title for inserting information like [Maverick A1] as this used by Launchpad's duplicate finding feature and will likely create false positives. Instead I'd tag the bug maverick, which would be done automatically if you report it with apport, and only include the image information (in the description) if it may be specific to that ISO and not the release as a whole. Hey Brian, Thanks for pointing that out. Wish someone had let me know through the Lucid cycle :-) I didn't realize that could muck with the duplicate checking, but I'll change behaviour appropriately. So Mark, don't do as I mentioned (at least WRT to teh subject line in a bug report. Follow Brian's advice instead) :-) Cheers, Jeff -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Second problem on firefox, sorry, forgot.
On Mon, Apr 5, 2010 at 20:02, irlandes brucemcgov...@earthlink.net wrote: I forgot. Also now depending upon where the cursor is, I get a big blinking bar all the way to the bottom, sometimes it is real wide. This started at the same time. I can eliminate it by clicking elsewhere. Reminder this is in Firefox 3.6.3 automatic update on 9.10, but that means there is some sick Firefox stuff out there just as we are ready to finalize 10.04. Before you get all bent out of shape and yell about how disgusting it all is, you should probably look at launchpad.net for any bugs, and open one... To be honest, I'm running 3.6.3 on a Lucid system and on a karmic system, and I've not had any issues at all with FF... I know my own example is not enough to be a representative, but I doubt that there is something so massively broken in FireFox... I'd be quicker to blame an addon you're running, or a video driver, or something else (something java related perhaps) than I would FF itself. Cheers Jeff -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: A follow up.
On Sun, Mar 28, 2010 at 11:48, Gary Mellor mellor.g...@yahoo.co.uk wrote: I've just checked the activity list for testing and I am interested in the following test areas: [1]. ISO testing (laptop) [2]. Laptop testing [3]. General testing (laptop) Cool... get to it ;-) 1: ISO testing is a great and easy way to start, IMHO. Download the isos, put them on disk or on USB sticks and just boot and go. Most of the ISO testing is geared toward testing the ISO itself, and the installer. You'll find test cases here: http://iso.qa.ubuntu.com and more specific cases (sometimes) as needed here: http://pairwise.qa.ubuntu.com 2: Laptop testing info can be found here: https://wiki.ubuntu.com/Testing/Laptop It's nice to have as many laptops as possible tested, given the vast differences in hardware across brands, and the fact that laptops can often have a lot of weird half-chipsets built into them. Cases like some video cards that may have the GPU from the video card family, but none of the onboard RAM... 3: General testing: My best advice, pick something and try it out and write bugs if it doesnt work. But pick something that's interesting to you, not just something at random. Otherwise, you'll get bored ;-) Good examples: if you like music, then test Rhythmbox a lot... if you like watching DVDs, then try the different codecs, and video players and test that they play DVDs and integrate properly into the desktop. Bugs are filed via Launchpad (http://launchpad.net) and here's an intro to reporting them: https://help.ubuntu.com/community/ReportingBugs I can only test on laptops as I do not have any desktop hardware. Nothing wrong with that... I do all my testing on an Alienware M15x (in virtual machines) and on a Lenovo S-10 netbook. My 'junker' is a HP 510 with 4GB RAM and an uprated hardrive (7200rpm as opposed to 5400rpm). This is x86 architecture. Other than the changes mentioned in terms of RAM and hardrive, everything else is standard. Your junker sounds like mine (4GB, Quad Core i7, 500GB SATAII, etc)... Given the size of your system, you could also do testing in Virtual Machines (look into KVM or VirtualBox). I do a LOT of ISO and Pairwise testing in VMs. It lets me run tests in parallel instead of one at a time. Plus I can create scenarios like multiple hard disks and NICs if I wish. My 'stable' laptop is a Lenovo G550 with 8GB RAM and a smaller but faster hardrive (320GB @ 7200rpm as opposed to 500GB @ 5400rpm). Sheesh... you people and your toys ;-) I need to bump mine to 8GB... one of these days, I suppose :) I'm happy to test on either really but would prefer to do General Testing on my stable machine and ISO and specific laptop testing on my junker. Well, remember what I said about virtualbox and KVM (that's kernel-based virtual machine, not keyboard-video-mouse). You can certainly do all sorts of ISO testing that way, in addition to doing it on real hardware. The real hardware tests are always better, as that helps get a bigger spread of hardware tested during any given cycle, but you'll find bugs just as quickly in a VM as you will on bare-metal. Cheers, Jeff -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
