Re: Introduction
2012/1/13 José Cardoso de Almeida > Hi, > > My name is José Almeida, and I recently joined this team to start giving > my contribution to the Ubuntu project. > > Could you kindly advise where should I begin. > > Thank you and regards, > José > -- > This message was sent from Launchpad by > =?utf-8?q?Jos=C3=A9_Cardoso_de_Almeida?= (https://launchpad.net/~cardozo) > to each member of the Ubuntu Testing Team team using the "Contact this > team" > link on the Ubuntu Testing Team team page > (https://launchpad.net/~ubuntu-testing). > For more information see > https://help.launchpad.net/YourAccount/ContactingPeople > Hi Jose, There are many different avenues to get involved in with Ubuntu. We are the QA team, and we're dealing with unity testing, iso testing, doing sru testing, etc. What are your interests? Hop on the #ubuntu-testing IRC channel and introduce yourself. We're happy to get you plugged in :-) You could also state your other interests and we'll try to point you to the right direction. All the best, -- Alex Lourie -- 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
Brandan I agree with you. I just noticed it and thought that it is important for us, the QA, to address. I hope to get it discussed with you guys :-). On Mon, Jan 9, 2012 at 7:43 PM, Brendan Donegan < brendan.done...@canonical.com> wrote: > Alex, > > Having such a 'bug' lying around isn't useful, so I closed it as invalid. > I agree we should discuss this issue of third-party software breaking and > you're right that it has echoes of Ubuntu Friendly/Hardware Certification > (you could say we need a type of 'Software Certification' as well as > 'Hardware Certification') > > I note that the bug reporter didn't offer the name of the commercial > software which broke for them as well, which isn't helpful. > > > On 09/01/12 17:31, Alex Lourie wrote: > > On Mon, Jan 9, 2012 at 6:29 PM, Gema Gomez < > gema.gomez-sol...@canonical.com> wrote: > >> 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 >> > > 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'd love to participate in a discussion on this topic, but generally the > idea I had is somewhat reminiscent of Friendly - to have a list of various > commercial software applications tested for each new release, to know where > we could have a problem. > > So, if you decide to talk about it while I'm absent, fine, I'll read > logs later. If I'm present - then we could have a discussion, or just start > to think about it. > > Cheers. > > -- > Alex Lourie > > > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Alex Lourie -- 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
On Mon, Jan 9, 2012 at 6:29 PM, Gema Gomez wrote: > 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 > 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'd love to participate in a discussion on this topic, but generally the idea I had is somewhat reminiscent of Friendly - to have a list of various commercial software applications tested for each new release, to know where we could have a problem. So, if you decide to talk about it while I'm absent, fine, I'll read logs later. If I'm present - then we could have a discussion, or just start to think about it. Cheers. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: #ubuntu-quality channel consolidated with #ubuntu-testing
On Mon, Jan 9, 2012 at 6:58 PM, C de-Avillez wrote: > Hello all, > > First of all, my apologies for those that subscribe to more than one > of the mailing lists in the To: list. > > We are consolidating the QA/testing presence on IRC; as such, we are > terminating the usage of #ubuntu-quality, and forwarding all > requests to join this channel to #ubuntu-testing. > > This is immediately effective. > > For those of you currently attached to #ubuntu-quality: please > disconnect from the channel, and join #ubuntu-testing instead. > > Please reply to the list(s) on any questions, or ask them on > #ubuntu-testing. > > Cheers, > > ..C.. > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > Great news. I never understood why would we need 2 different channels like that. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: New to Distro Testing
On Tue, Jan 3, 2012 at 7:32 AM, cdwolf wrote: > Hey guys, I'm new to testing the new Ubuntu's while they are in > development. I was just wondering if you had any tips before I "dive in" > so to speak. > -- > This message was sent from Launchpad by > cdwolf (https://launchpad.net/~charlespoetwolf) > to each member of the Ubuntu Testing Team team using the "Contact this > team" > link on the Ubuntu Testing Team team page > (https://launchpad.net/~ubuntu-testing). > For more information see > https://help.launchpad.net/YourAccount/ContactingPeople > Hi there! Welcome to testing Ubuntu! If you have any specific questions, hop in to #ubuntu-testing on freenode, and we'll be happy to help you out. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re:
Sure! On Mon, Jan 2, 2012 at 1:45 PM, mohammad awwad wrote: > thanks for the information , i hope we communicate more :) > > > On Mon, Jan 2, 2012 at 1:42 PM, Alex Lourie wrote: > >> On Mon, Jan 2, 2012 at 1:30 PM, mohammad awwad wrote: >> >>> i think the team is Unapproved Team , is there any possible way to make >>> a new team or is there some conditions to make one that can be approved ? >>> >>> i started to help in testing >>> >>> On Mon, Jan 2, 2012 at 1:17 PM, Alex Lourie wrote: >>> >>>> On Mon, Jan 2, 2012 at 12:50 PM, mohammad awwad wrote: >>>> >>>>> hi alex >>>>> >>>>> >>>>> i'd like to help in QA activities , but is there something i can do , >>>>> since i'm a student in the hashemite university , i think i can make some >>>>> events for the ubuntu i just need some information about what i suppose to >>>>> do if you could help me >>>>> >>>>> >>>>> On Sun, Jan 1, 2012 at 10:56 PM, Alex Lourie wrote: >>>>> >>>>>> On Sun, Jan 1, 2012 at 10:49 PM, mohammad awwad wrote: >>>>>> >>>>>>> hi , my name is Mohammad Awwad i'm from Jordan , i like to help >>>>>>> ubuntu , is there any possible way to do that ? >>>>>>> >>>>>>> -- >>>>>>> Ubuntu-qa mailing list >>>>>>> Ubuntu-qa@lists.ubuntu.com >>>>>>> Modify settings or unsubscribe at: >>>>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >>>>>>> >>>>>>> >>>>>> Hi Mohammad >>>>>> >>>>>> Welcome to the Ubuntu QA! Are you interested in helping in QA >>>>>> activities? >>>>>> >>>>>> If not, just let us know what would you like to do, and we'll help >>>>>> you to find the right people to talk to. >>>>>> >>>>>> Otherwise, head over to [1] and join us! :-) >>>>>> >>>>>> [1] http://wiki.ubuntu.com/QATeam >>>>>> >>>>>> -- >>>>>> Alex Lourie >>>>>> >>>>> >>>>> >>>> Hi Mohammad >>>> >>>> If you like to help with QA activities, the easiest way would be ISO >>>> image testing. You can read about this at [1]. Additionally, you can find a >>>> more full list at [2]. >>>> >>>> Finally, if you would like to help making events for Ubuntu, you can >>>> contact Jordan Ubuntu Local group [3]. >>>> >>>> [1] https://wiki.ubuntu.com/Testing/ISO >>>> [2] https://wiki.ubuntu.com/Testing/Activities >>>> [3] http://loco.ubuntu.com/teams/ubuntu-jordan >>>> >>>> If you still have questions, don't hesitate to ask! >>>> >>>> -- >>>> Alex Lourie >>>> >>> >>> >> It is not important for the team to be "approved" to have organized >> events - if you like to have an event, just organize it! >> >> You could talk to loco council at loco.ubuntu.com about requirements to >> make the team "official". >> >> And, of course, welcome to QA! >> >> :-) >> >> -- >> Alex Lourie >> > > -- Alex Lourie -- 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, Jan 2, 2012 at 1:30 PM, mohammad awwad wrote: > i think the team is Unapproved Team , is there any possible way to make a > new team or is there some conditions to make one that can be approved ? > > i started to help in testing > > On Mon, Jan 2, 2012 at 1:17 PM, Alex Lourie wrote: > >> On Mon, Jan 2, 2012 at 12:50 PM, mohammad awwad wrote: >> >>> hi alex >>> >>> >>> i'd like to help in QA activities , but is there something i can do , >>> since i'm a student in the hashemite university , i think i can make some >>> events for the ubuntu i just need some information about what i suppose to >>> do if you could help me >>> >>> >>> On Sun, Jan 1, 2012 at 10:56 PM, Alex Lourie wrote: >>> >>>> On Sun, Jan 1, 2012 at 10:49 PM, mohammad awwad wrote: >>>> >>>>> hi , my name is Mohammad Awwad i'm from Jordan , i like to help >>>>> ubuntu , is there any possible way to do that ? >>>>> >>>>> -- >>>>> Ubuntu-qa mailing list >>>>> Ubuntu-qa@lists.ubuntu.com >>>>> Modify settings or unsubscribe at: >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >>>>> >>>>> >>>> Hi Mohammad >>>> >>>> Welcome to the Ubuntu QA! Are you interested in helping in QA >>>> activities? >>>> >>>> If not, just let us know what would you like to do, and we'll help you >>>> to find the right people to talk to. >>>> >>>> Otherwise, head over to [1] and join us! :-) >>>> >>>> [1] http://wiki.ubuntu.com/QATeam >>>> >>>> -- >>>> Alex Lourie >>>> >>> >>> >> Hi Mohammad >> >> If you like to help with QA activities, the easiest way would be ISO >> image testing. You can read about this at [1]. Additionally, you can find a >> more full list at [2]. >> >> Finally, if you would like to help making events for Ubuntu, you can >> contact Jordan Ubuntu Local group [3]. >> >> [1] https://wiki.ubuntu.com/Testing/ISO >> [2] https://wiki.ubuntu.com/Testing/Activities >> [3] http://loco.ubuntu.com/teams/ubuntu-jordan >> >> If you still have questions, don't hesitate to ask! >> >> -- >> Alex Lourie >> > > It is not important for the team to be "approved" to have organized events - if you like to have an event, just organize it! You could talk to loco council at loco.ubuntu.com about requirements to make the team "official". And, of course, welcome to QA! :-) -- Alex Lourie -- 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, Jan 2, 2012 at 12:50 PM, mohammad awwad wrote: > hi alex > > > i'd like to help in QA activities , but is there something i can do , > since i'm a student in the hashemite university , i think i can make some > events for the ubuntu i just need some information about what i suppose to > do if you could help me > > > On Sun, Jan 1, 2012 at 10:56 PM, Alex Lourie wrote: > >> On Sun, Jan 1, 2012 at 10:49 PM, mohammad awwad wrote: >> >>> hi , my name is Mohammad Awwad i'm from Jordan , i like to help ubuntu >>> , is there any possible way to do that ? >>> >>> -- >>> Ubuntu-qa mailing list >>> Ubuntu-qa@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >>> >>> >> Hi Mohammad >> >> Welcome to the Ubuntu QA! Are you interested in helping in QA activities? >> >> If not, just let us know what would you like to do, and we'll help you to >> find the right people to talk to. >> >> Otherwise, head over to [1] and join us! :-) >> >> [1] http://wiki.ubuntu.com/QATeam >> >> -- >> Alex Lourie >> > > Hi Mohammad If you like to help with QA activities, the easiest way would be ISO image testing. You can read about this at [1]. Additionally, you can find a more full list at [2]. Finally, if you would like to help making events for Ubuntu, you can contact Jordan Ubuntu Local group [3]. [1] https://wiki.ubuntu.com/Testing/ISO [2] https://wiki.ubuntu.com/Testing/Activities [3] http://loco.ubuntu.com/teams/ubuntu-jordan If you still have questions, don't hesitate to ask! -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Introduction
On Mon, Jan 2, 2012 at 7:02 AM, Scott wrote: > Hi, > >I am following the "How do I get Involved" on the wiki and it suggested > I introduce myself on this mailing list and list my goals and Interest, so > I am. :) > >I have been testing Ubuntu for a while now and based on the activities > list I like doing General Testing. I like to take a release as early as I > can in the Alpha stage and use it as my main OS. As long as there are no > show stopper bugs for me I will continue to use it and report any bugs I > find. This type of bug testing interest me most, but depending on my time > I would like to look at other testing that can help. > >My goal is to simply give back to the Ubuntu community from which have > provided me a product I depend on so much. > > -- > Your friend, > Scott > > > -- > Ubuntu-qa mailing list > 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> > Hi Scott Thanks for expressing interest in Ubuntu QA. If you like General Testing, you've come to the right place!! We have a lot of such activities and you can participate in any way that suites you. You can read about these at the wiki [1]. Additionally, you can hop into #ubuntu-testing on Freenode IRC for a chat on participating in other QA activities. Just remember, that it is still a holidays period, so not many may be available for chat yet. Currently, there is testing going on for the Precise Pangolin Alpha 1 release - the test tracker is [2] and you can ask on #ubuntu-testing if you aren't sure how to use it. [1] http://wiki.ubuntu.com/QATeam [2] http://iso.qa.ubuntu.com/qatracker/milestones/205/builds -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re:
On Sun, Jan 1, 2012 at 10:49 PM, mohammad awwad wrote: > hi , my name is Mohammad Awwad i'm from Jordan , i like to help ubuntu , > is there any possible way to do that ? > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > Hi Mohammad Welcome to the Ubuntu QA! Are you interested in helping in QA activities? If not, just let us know what would you like to do, and we'll help you to find the right people to talk to. Otherwise, head over to [1] and join us! :-) [1] http://wiki.ubuntu.com/QATeam -- Alex Lourie -- 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
Hi Phil Just join the group and talk to jibel to approve you :-) On Wed, Dec 28, 2011 at 10:01 AM, Phill Whiteside 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 < > 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>> 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 >> > > > > -- > https://wiki.ubuntu.com/phillw > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Blueprints involvement
On Thu, Dec 15, 2011 at 6:52 PM, Gema Gomez wrote: > 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 > No problem by me, Gema, go ahead. -- Alex Lourie -- 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 Fri, Dec 16, 2011 at 6:57 AM, Nicholas 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 > 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 -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
QA wiki update
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 -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Short test cases rewrite guide
On Tue, Dec 13, 2011 at 11:05 AM, Brendan Donegan < brendan.done...@canonical.com> wrote: > On 13/12/11 06:11, Alex Lourie wrote: > > On Tue, Dec 13, 2011 at 12:24 AM, Charlie Kravetz < > c...@teamcharliesangels.com> wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On Mon, 12 Dec 2011 23:56:10 +0200 >> Alex Lourie wrote: >> >> > Hi all >> > >> > I've come up with a short (and probably too obvious) guide for rewriting >> > test cases [1]. Please let me know what you think. >> > >> > I also linked to it on the TasksPrecise page [2], so if someone looses >> the >> > link, you can always find the guide there. >> > >> > It is not meant to be a generic guide for writing good test cases yet, I >> > think to write that one later. Or maybe I'm wrong, and they should be >> one >> > and the same. >> > >> > Thanks. >> > >> > [1] https://wiki.ubuntu.com/QATeam/TasksPrecise/TestCasesRewrite >> > [2] https://wiki.ubuntu.com/QATeam/TasksPrecise >> > >> >> That looks good from here. > > > Hi Charlie > > Thank you the feedback. > > >> Are we re-writing all test cases? > > > Hopefully, yes. > > >> In the midst of this, I would hope we will also explain the differences >> when >> testing. For example, Ubuntu, one waits for "Try Ubuntu" "Install >> Ubuntu" to appear. In Xubuntu, one selects from the CD menu directly to >> try or install. >> > I'd just like to point out here that the installation for Xubuntu is a > *seperate* test case. No-one should ever be attempting to explain the > differences in behavior of two different systems in one test case. > > +1! Absolutely correct. > >> > Of course, this should be reflected in a specific test case. If it's > not, it's a "bug" > in a test case from my point of view and should be fixed. > > >> - -- >> Charlie Kravetz >> Linux Registered User Number 425914 [http://counter.li.org/] >> Never let anyone steal your DREAM. [http://keepingdreams.com] >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.11 (GNU/Linux) >> >> iQEcBAEBAgAGBQJO5n8QAAoJEFNEIRz9dxbAEqQH/0QJQCxpicHdaW6+maRCP76e >> afH43KdTj6PlTZVu1hdpg0m4RiZZyUOBMTmhM++lbHiqc4akYcohVVg50WBS05M9 >> 42Xhjg3UGJBNUDYtqe6NWuUFg5MsXO7A97IUPyKHePDL2gEZKC4vwu4gUn6NleoK >> oJ8bJJT0JcSLocWbir5T/2EL4H99+hO7KSwWjHyEf/mfGa45JVZiWdxaCtrtScYM >> tyj05adx4hYiK3qpYXDG1ezU+t+H9Y/8zVNvv35j0TTYXt7VLpH32hcrHARHvkCN >> FAgS7FX7+De2QbmRRUhMjvvn2kYzekbXNp8TQMhQzFUtKAkpX1qfHbbblen8w4A= >> =vLbA >> -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 >> > > > -- > Alex Lourie > > > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Alex Lourie -- 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
On Tue, Dec 13, 2011 at 11:05 AM, Javier Domingo wrote: > Very interesting and enjoying platform, I would improve going backward > function a little more, as if done in js doesn't store the previous state. > Its quite smart thought, > > Javier Domingo > > Javier You can look at the code on github, it's still quite in development. > > > 2011/12/13 Alex Lourie > >> On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez < >> gema.gomez-sol...@canonical.com> wrote: >> >>> 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 >>> >> >> I know that some of you already registered on the demo site, here's the >> link https://cc.oddsites.net where one could play with Case Constructor. >> >> I'm liking it so far. >> >> -- >> Alex Lourie >> >> -- >> Ubuntu-qa mailing list >> Ubuntu-qa@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >> >> > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Alex Lourie -- 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
On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez wrote: > 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 > I know that some of you already registered on the demo site, here's the link https://cc.oddsites.net where one could play with Case Constructor. I'm liking it so far. -- Alex Lourie -- 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
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 -- 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
On Tue, Dec 13, 2011 at 8:12 AM, Alex Lourie wrote: > On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez < > gema.gomez-sol...@canonical.com> wrote: > >> 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 >> > > > Sorry about previous. I meant to add: * Test cases versioning. The bugs on test cases can be actually opened on Launchpad, but we need to think about proper flow of fixing/closing the bug. -- Alex Lourie -- 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
On Mon, Dec 12, 2011 at 5:02 PM, Gema Gomez wrote: > 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 > How about test cases versioning? What is the test case needs fixing? -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Short test cases rewrite guide
On Tue, Dec 13, 2011 at 12:24 AM, Charlie Kravetz < c...@teamcharliesangels.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, 12 Dec 2011 23:56:10 +0200 > Alex Lourie wrote: > > > Hi all > > > > I've come up with a short (and probably too obvious) guide for rewriting > > test cases [1]. Please let me know what you think. > > > > I also linked to it on the TasksPrecise page [2], so if someone looses > the > > link, you can always find the guide there. > > > > It is not meant to be a generic guide for writing good test cases yet, I > > think to write that one later. Or maybe I'm wrong, and they should be one > > and the same. > > > > Thanks. > > > > [1] https://wiki.ubuntu.com/QATeam/TasksPrecise/TestCasesRewrite > > [2] https://wiki.ubuntu.com/QATeam/TasksPrecise > > > > That looks good from here. Hi Charlie Thank you the feedback. > Are we re-writing all test cases? Hopefully, yes. > In the midst of this, I would hope we will also explain the differences > when > testing. For example, Ubuntu, one waits for "Try Ubuntu" "Install > Ubuntu" to appear. In Xubuntu, one selects from the CD menu directly to > try or install. > > Of course, this should be reflected in a specific test case. If it's not, it's a "bug" in a test case from my point of view and should be fixed. > - -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEcBAEBAgAGBQJO5n8QAAoJEFNEIRz9dxbAEqQH/0QJQCxpicHdaW6+maRCP76e > afH43KdTj6PlTZVu1hdpg0m4RiZZyUOBMTmhM++lbHiqc4akYcohVVg50WBS05M9 > 42Xhjg3UGJBNUDYtqe6NWuUFg5MsXO7A97IUPyKHePDL2gEZKC4vwu4gUn6NleoK > oJ8bJJT0JcSLocWbir5T/2EL4H99+hO7KSwWjHyEf/mfGa45JVZiWdxaCtrtScYM > tyj05adx4hYiK3qpYXDG1ezU+t+H9Y/8zVNvv35j0TTYXt7VLpH32hcrHARHvkCN > FAgS7FX7+De2QbmRRUhMjvvn2kYzekbXNp8TQMhQzFUtKAkpX1qfHbbblen8w4A= > =vLbA > -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 > -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Short test cases rewrite guide
Hi all I've come up with a short (and probably too obvious) guide for rewriting test cases [1]. Please let me know what you think. I also linked to it on the TasksPrecise page [2], so if someone looses the link, you can always find the guide there. It is not meant to be a generic guide for writing good test cases yet, I think to write that one later. Or maybe I'm wrong, and they should be one and the same. Thanks. [1] https://wiki.ubuntu.com/QATeam/TasksPrecise/TestCasesRewrite [2] https://wiki.ubuntu.com/QATeam/TasksPrecise -- Alex Lourie -- 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
On Sat, Dec 10, 2011 at 7:56 PM, Gema Gomez wrote: > 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 >
Re: Gherkin DSL for testcase description and automation
On Sat, Dec 10, 2011 at 11:44 AM, Руаньяк wrote: > 2011/12/9 Gema Gomez : > > +1 to brendand for putting it so clearly. > > > > 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 > Here is a quick and dirty example. I marked comments with #, however, > they should be removed for automation suite. > > -- > Feature: Ubuntu Full Install > > Scenario: Default installation > > When I boot with Live CD > Then I see a desktop > And 'Install Ubuntu' icon is present > > When I double click 'Install Ubuntu' icon > Then Ubuquity starts #here we can check main window etc. > > When Welcome screen appears# add steps to check welcome screen > And I click 'Forward' button > > When 'Preparing to install Ubuntu' screen appears > Then Checkmark 'Your system have at least the amount a space indicated' is > set > And Checkmark 'Is plugged to a power source' is set > And Checkmark 'Is connected to the Internet' is set > > When I click 'Forward' > Then 'Allocate drive space' screen appears > > When I select 'Erase Disk and install Ubuntu' > Then option is selected # rewrite me, i look stupid! > > When I click 'Forward' > Then 'Erase disk and install Ubuntu' screen appears > And Selected item in 'Select drive' list is the drive on the chart > And Full drive space is allocated > > When I click 'Forward' button > Then 'Where are you?' screen appears > And Current city is set to 'Minsk' #Use variables here! > And Current timezone is set to 'GMT+3' #And here! > > When I click on 'London' city on the map > Then Current timezone is set to 'GMT' > And Current city is set to 'London' > > When I input 'Par' in city textbox > Then Suggestions dropdown list is opened > And Suggestion list contains 'Paris' item > > When I select 'Paris' from suggestion list > Then Current city is set to 'Paris' > And Current timezone is set to 'GMT+1' #Is it? Correct if it is not > > When I click 'Forward' button > Then 'Keyboard layout' screen appears > > When I select 'EN' layout #review me! > And I select 'EN-GB' variant #and me too, please! > And I press 't' button > Then 't' symbol appears in verification textbox #rewrite, looks ugly, huh? > > When I click 'Detect Keyboard Layout' button > And I answer all questions #expand me! > Then Proposed keyboard layout is 'En, En-gb' > > When I click 'Forward' button > Then 'Who are you?' screen appears > > When I input user details#expand - I input 'name' > as name etc. > And I click 'Forward' > Then Installation screen appears > > When I click left arrow on the side of the slide > Then Next slide is displayed > > When I click right arrow on the side of the slide > Then Previous slide is displayed > > When I wait for 1 minute > Then Next slide is displayed > > When Installer has finished its tasks > And I click 'Restart now' option > Then 'something about remove disk' dialog appears #oh my, its been > long since I installed Ubuntu! > > When I remove disk > And I press Enter > Then machine reboots > > When Grub is displayed > And Plymouth displays fancy animation > Then Login prompt is displayed > > When I input required credentials# expand - I input '' as login > etc. > Then User is logged in > > -- > Vadim Rutkovsky > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > Hm, this seems to be quite interesting. 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? 2. How would one execute this in LiveCD environment? 3. Is it possible to run something like that in automated VM environment? Thanks. -- Alex Lourie -- 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
mation with Gherkin DSL. > > > > There also some more interesting stuff in Gherkin - such as tagging, > > step argument transform and step reusing - I guess, I can describe > > them in other posts, if this whole propasl will be interesting. > > > > Hope to hear for more ideas and thoughts. > > Vadim Rutkovsky > > > > - > > Links: > > Gherkin DSL examples and structure: > > https://github.com/cucumber/cucumber/wiki/Gherkin > > http://code.google.com/p/spectacular/wiki/WritingBDDTests > > > http://en.wikipedia.org/wiki/Behavior_Driven_Development#Application_examples_in_the_Gherkin_language > > > > Sample automation code for GCalc: > > https://code.launchpad.net/~roignac/+junk/freshen_mago > > > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > -- Alex Lourie -- 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 Fri, Dec 9, 2011 at 12:50 AM, Gema Gomez wrote: > 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. > > Sure, I didn't mean to patronise by no means. > > > > 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 completely agree. I don't think that there is more or less important contributors, or that someones' work is more professional than someone else's. I just meant that the selection of specific categories would be a result of the specifics of our work. In some cases the importance of the task would mean a category (such as Urgent, Very Important, Important, Regular, Optional, etc), and in case of our QA, at least c
Re: Test Cases Spreadsheet
On Thu, Dec 8, 2011 at 4:45 PM, Alex Lourie wrote: > On Thu, Dec 8, 2011 at 3:45 PM, Gema Gomez < > gema.gomez-sol...@canonical.com> wrote: > >> >> 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. >> >> > I second that. I recommend prioritising here, so I believe it is better to > begin with ISO test cases, then continue to application test cases. > Moreover, we should probably prioritise the ISO cases as well, so we > concentrate on more important ones first. > > OK, so thinking about this further, I came up with the following: 1. As I previously recommended, work on ISO tracker test cases first, deal with everything else later. 2. Select few representing flavours from the list on [1] 3. Rewrite mandatory test cases. 4. When 3. above is done, rewrite the run-once test cases. 5. When 4. above is done, rewrite optional test cases. 6. Repeat 3-5 for other flavours until all test cases for ISO testing are rewritten. 7. Approve all tests. ( I recommend at least one peer review per test, just to be on a safe side). Feedback on this would be extremely helpful, especially I'd like to have the consensus on the first bunch of flavours to rewrite (I guess, main Ubuntu i386 Desktop/server, Kubuntu and Xubuntu should get there). I'd set a first bunch to 5-7, so we see how it goes. Thanks [1] http://91.189.93.73/qatracker/milestones/205/builds -- Alex Lourie -- 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 Thu, Dec 8, 2011 at 7:57 PM, Gema Gomez 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 That's OK, we can handle the jargon. I think that in our case, categories should represent our way of work. 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 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. So it would go as this: * *Applications* (for application related tests, such as testing editors, browsers, etc). * *System* (for testing system built ins, such as, maybe, services scripts, global/local settings, default system configurations, etc) * *Hardware* (for testing hardware components) * *Install* (for test cases performed during the installation process) * *Upgrade* (for test cases performed during the upgrade process) ** CasesMods (I have no idea what it is right now, so if anyone does please let us know).* I am going to use this selection on the Test Cases Rewriting document, and if anything changes we'll update accordingly. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Test Cases categories
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 -- 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 Thu, Dec 8, 2011 at 3:45 PM, Gema Gomez wrote: > 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. > > I second that. I recommend prioritising here, so I believe it is better to begin with ISO test cases, then continue to application test cases. Moreover, we should probably prioritise the ISO cases as well, so we concentrate on more important ones first. > 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. > > Maybe we should add categories to the spreadsheet document. Or, we can probably do some kind of TestID->Category mapping. > 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 > Awesome! I'll try to push it a bit over social networks too. -- Alex Lourie -- 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 Thu, Dec 8, 2011 at 1:24 PM, 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 > > -- > 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 > 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 -- 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 Thu, Dec 8, 2011 at 2:27 PM, Steven Leeman wrote: > 2011/12/8 Brendan Donegan > >> On 08/12/11 12:04, Steven Leeman wrote: >> >> >> >> 2011/12/8 Brendan Donegan >> >>> >>> >>> The recommend way to follow up on a comment is to make a new comment on >>> the same cell, but let's see how this goes since if one cell gets lots >>> of comments it could become cumbersome. >>> >>> >> - about comments is they can't be "printed" or "listed" as far as I >> know? >> I only know about the "hover" method to see them... >> >> >> >>> -- >>> Ubuntu-qa mailing list >>> Ubuntu-qa@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >>> >> >> That's true. The only way to do this would be to put them in a separate >> field as we were about to do. This has other disadvantages such as it being >> ambiguous as to which column the commenter is commenting on. I'd love to >> hear other suggestions if you think this is a big weakness at the moment. >> This all highlight the need to have a proper test case management tool as >> soon as possible. >> >> Also, did you intend to reply just to me? This comment seems like >> something that would be useful to send to the whole list. >> >> Thanks, >> > > I've put it on the list :-) > > you can add more than 1 sheet ... a sheet called "comments" where you can > repeat your launchpad id, the sheet/column/row you want to comment to and > the actual comment? > you can then sort on "id" or on column/row to find all comments from a > certain person...or for a certain field... > > I'm not a "chat" person... "how many" people would be working on this > excel? > also the commenting system is currently to work out a "template" ? > But still it's easier for the person who will have to make a summary > against next weeks meeting to not have to hover each cell > ... > > Greetz, > Steven > > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > OK, we'll need to see how it goes. -- Alex Lourie -- 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
On Mon, Dec 5, 2011 at 6:24 PM, 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. > 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 > Hi Gema, all I'll be interested in : 1. I'd like to participate in the discussions. 2. I really think it's important. Making concise and clear test cases would help us tremendously to convert some of them to automatic tests and also, maybe, bring new people
Re: Greatings!
On Thu, Dec 1, 2011 at 11:42 AM, Amaro Maguni wrote: > Hello, everone! > > My name is Amaro Maguni (nickname: Lamech De Seth), i live in Maputo - > Mozambique (Africa). > My e-mail address is amaro,mag...@hotmail.com (the one i signed in with > in this list), > but my account was hacked and i can't have access to it, that's way i am > sendind this e-mail > with this alternative e-mail address. Sorry for that > I am a Linux (Ubuntu) user for two years now, and a Linux enthusiast since > 2002. > I joined this list because i'd like to learn, participate and help the > Ubuntu cummunity. > > Hope to get/give good things from/to you all and and a lote of hard work > too. > > Regards > > Amaro Maguni > > -- > Ubuntu-qa mailing list > 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> > Hi Amaro Thanks for expressing interest in Ubuntu QA. Right now you can join the following communications channels for guidance: * #ubuntu-bugs on Freenode IRC, for help on managing and raising bugs * #ubuntu-testing on Freenode IRC, for help on participating in QA activities (ISO testing mainly) The QA wiki is here - https://wiki.ubuntu.com/QATeam The Bug Squad (bug management community) is here - https://wiki.ubuntu.com/BugSquad Currently, there is testing going on for the Precise Pangolin Alpha 1 release - the test tracker is here : http://91.189.93.73/qatracker/milestones/205/builds and you can ask on #ubuntu-testing if you aren't sure how to use it. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: monitor brightness can't be dimmed
On Tue, Nov 15, 2011 at 10:59 AM, Alexander Vinbæk Strand < alexstra...@gmail.com> wrote: > ** > How to file bugs? I want to send some bug reports but doesn't know how to > do it. > Since you are going to file bugs I think you also know how. > > > Den 12. nov. 2011 20:47, skrev Alex Lourie: > > On Sat, Nov 12, 2011 at 9:41 PM, CESAR TABLAS wrote: > >> Yes, through the laptop buttons and also through System Settings - >> Screen - Brightness. Both don't work. >> >> I will file the bug report as you mentioned. It'll be my first time, >> though. >> >> Thank you, Cesar Tablas >> >>-- >> *From:* Alex Lourie >> *To:* CESAR TABLAS >> *Sent:* Friday, November 11, 2011 12:08:46 PM >> *Subject:* Re: monitor brightness can't be dimmed >> >> On Fri, Nov 11, 2011 at 5:50 PM, CESAR TABLAS wrote: >> >> I am running ubuntu 11.10 on a Gateway NV55C with integrated Intel HD >> graphics, and I am not able to dim the monitor. Any suggestion? >> >> -- >> Ubuntu-qa mailing list >> Ubuntu-qa@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >> >> >> Cesar >> >> How do you try to dim the monitor? Are you using the buttons on the >> laptop? If so, I recommend filing a bug about it. >> >> -- >> Alex Lourie >> >> >> > Hey Cesar > > Let us know if you have trouble filing a proper bug report. > Alternatively, you can hop into #ubuntu-bugs and get help there in > [approximately] real time. > > -- > Alex Lourie > > > Hi Alexander There's a thorough explanation on Ubuntu Wiki [1] how to file bugs, but in general it involves registering a Launchpad account, logging into the system and creating a new bug report. There are other, more automated, ways to file bugs, which are all explained on the wiki page. Let us know if you don't understand how to do it, we'll try to help you with it. [1] https://help.ubuntu.com/community/ReportingBugs -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: monitor brightness can't be dimmed
On Sat, Nov 12, 2011 at 9:41 PM, CESAR TABLAS wrote: > Yes, through the laptop buttons and also through System Settings - Screen > - Brightness. Both don't work. > > I will file the bug report as you mentioned. It'll be my first time, > though. > > Thank you, Cesar Tablas > > ------ > *From:* Alex Lourie > *To:* CESAR TABLAS > *Sent:* Friday, November 11, 2011 12:08:46 PM > *Subject:* Re: monitor brightness can't be dimmed > > On Fri, Nov 11, 2011 at 5:50 PM, CESAR TABLAS wrote: > > I am running ubuntu 11.10 on a Gateway NV55C with integrated Intel HD > graphics, and I am not able to dim the monitor. Any suggestion? > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > > Cesar > > How do you try to dim the monitor? Are you using the buttons on the > laptop? If so, I recommend filing a bug about it. > > -- > Alex Lourie > > > Hey Cesar Let us know if you have trouble filing a proper bug report. Alternatively, you can hop into #ubuntu-bugs and get help there in [approximately] real time. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Introducing myself
On Thu, Nov 10, 2011 at 11:02 PM, Daniels Pitkevics < daniels.pitkev...@inbox.lv> wrote: > Good evening! > > I am Daniel, almost done with joining the Ubuntu team in testing software. > I am young man from Latvia, studying Computer Science, so I am interested > in these kind of things. > Why I want to join this community? To improve my knowledge, to improve the > quality of ubuntu and to help people who don't understand this OS to > encourage them to try something new, like, Ubuntu. > I am interested in Operating Systems, how are they created, how can I > modify them, so GNU/Linux is the most open OS for this purpose, also I am > interested in programming - web pages (PHP, MySQL) and real programming > with C++. Just learning, but already know what is what. > And interests not related with computing are sports, travelling and now > for a while - looking for a job. > Anyway, thank you for this chance, I hope I will be able to help Ubuntu. > > Best regards, > Daniels Pitkevičs > > > > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > Hey Daniel Welcome to the Ubuntu QA! We hope you'll have a great time with us. You can ask here any questions you have and we'll try to help you as much as we can. Meanwhile, you can look over the QA team activities [1], and start participating in whatever you like the most! Cheers! [1] https://wiki.ubuntu.com/Testing/Activities -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Suggestions for ISO tracker
Hi Steven Thank you for the comments. Your suggestion does address both points, and yes, I believe that better integration would be beneficial. But I see the wiki as the resource and the tracker as its consumer, so I actually like the content separation. After all, the ISO tracker may be not the only "customer" of test descriptions. What I would like though is to have the option to update a result of each subtest I perform separately. Also, I believe it would be better to see the instructions directly on the test page in tracker, and not having to use the separate link. And the last thing: for example, on the page [1], there are two absolutely same links: one is called "Live session" and its icon is a page with a ranch key (what that should mean by the way?) and the second is "*Additional instructions are available for this testcase, click here to read them.<http://testcases.qa.ubuntu.com/Install/DesktopLiveSession>", *just below*. *What is the point to have them both? I think one of them definitely should be removed. [1] - http://iso.qa.ubuntu.com/qatracker/result/4330/3 On Wed, Aug 4, 2010 at 5:11 AM, Steven wrote: > I second this, on both items. > > 1) There are multiple tests per test case, i.e. the Live Session test case > has three sub-tests, each of which can be passed or failed (Live Session > Start, Live Session Finish, and Live Session Persistence). These sub-tests > should be passable or failable, not the umbrella Live Session test, in case > one is passed and another is failed. > > 2) "Additional instructions are available for this testcase, click here to > read them." makes it sound like it's optional to read how to perform the > tests. "Additional" should be removed. How can we provide consistent result > reports if people might not be following the same procedures? > > Ideally iso.qa.ubuntu.com and testcases.qa.ubuntu.com should be > integrated, such that clicking "Live Session" on iso.qa.ubuntu.com opens > another list of testcases from testcases.qa.ubuntu.com, and clicking on > these gives the instructions from testcases.qa.ubuntu.com along with the > Reporter/Last Update/Bugs/Comments table from iso.qa.ubuntu.com below it, > and the user's report below that. > > Basically instead of just having "Ubuntu Desktop i386 -> Live Session", it > should be "Ubuntu Desktop i386 -> Live Session -> Live Session Start". > > This seems like an efficient solution to your points, Alex. What do you > think about it? Anyone else have any comments about this structure? > > -Steven > > > On Sun, Jul 25, 2010 at 5:22 AM, Alex Lourie wrote: > >> Hello QA crowd >> >> I had a couple suggestions for ISO tracker: >> >> 1. I noticed there are few tests that include multiple different checks. >> For example, within one test in server ISO testing there are 2 KVM >> installations, 1 VMWare ESX installation and 1 VMWare server installation. >> While being similar they are different, and having run one check (VMWARE ESX >> - the only system I have) I still cannot provide my results as not all >> checks are finished, so the test is not completed. >> >> I suggest splitting such complex tests into smaller tests, so each of them >> could be tested on its own. >> >> 2. It is not really convenient to open the test, and see there nothing to >> do. As an experienced user I noticed the link to wiki pages, which, of >> course, have the test steps and the success criteria. But I believe it would >> be more obvious and convenient to have all steps directly available within >> the test page. >> >> This, of course, requires development, and that's why I asked if redesign >> is planned in a near future. >> >> I'll be happy for any comments. >> >> -- >> Alex Lourie >> >> -- >> Ubuntu-qa mailing list >> Ubuntu-qa@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa >> >> > -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Suggestions for ISO tracker
Hello QA crowd I had a couple suggestions for ISO tracker: 1. I noticed there are few tests that include multiple different checks. For example, within one test in server ISO testing there are 2 KVM installations, 1 VMWare ESX installation and 1 VMWare server installation. While being similar they are different, and having run one check (VMWARE ESX - the only system I have) I still cannot provide my results as not all checks are finished, so the test is not completed. I suggest splitting such complex tests into smaller tests, so each of them could be tested on its own. 2. It is not really convenient to open the test, and see there nothing to do. As an experienced user I noticed the link to wiki pages, which, of course, have the test steps and the success criteria. But I believe it would be more obvious and convenient to have all steps directly available within the test page. This, of course, requires development, and that's why I asked if redesign is planned in a near future. I'll be happy for any comments. -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re:
As far as my experience goes, most users will never read the description and will keep mailing such messages anyway. On Wed, Jul 21, 2010 at 3:29 AM, Charlie Kravetz wrote: > On Tue, 20 Jul 2010 15:23:31 -0700 > Brian Murray wrote: > > > On Mon, Jul 12, 2010 at 04:31:09PM -0400, Mackenzie Morgan wrote: > > > On Sun, Jul 11, 2010 at 9:09 PM, Bradley Spearpoint > > > wrote: > > > > i would like a ubuntu disk sent to me please > > > > > > You can request CDs from http://shipit.ubuntu.com > > > > > > This list is for the quality assurance team. > > > > I wonder if there something about the list name / description that could > > be clarified to prevent messages like this. At lists.ubuntu.com it > > currently says: > > > > Ubuntu Quality Assurance discussion list > > > > Any ideas on what might help? > > > > Thanks, > > -- > > Brian Murray > > Ubuntu Bug Master > > Many think of Quality Assurance as the place to resolve issues, since > any issue is a degradation of quality. Perhaps something like: > > Ubuntu Quality Assurance (bug triage, testing, etc) discussion list > > would more clearly define it while keeping it short. > > -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > > -- > Ubuntu-qa mailing list > Ubuntu-qa@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa > > -- Alex Lourie -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Invitation to join 10.04 Alpha 1 testing
Guys Why does [1] say that Alpha 1 of Lucid Lynx was issued on May 14th, 2009? :-) Alex. [1] http://www.ubuntu.com/testing -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
