Application testing for the new development cycle

Willem Hobers whobers at gmail.com
Fri May 18 15:12:47 UTC 2018


I did the test-case for Gigolo (ID 1587). I have reported some test-case 
issues, and also some issues with gigolo itself. Please tell me if 
there's any more information needed or if I have not followed the 
instructions below correctly.

Willem


Op 17-05-18 om 22:45 schreef flocculant:
>
> During this new 6 month cycle we are hoping to ramp up testing of 
> applications - separate from testing ISO's.
>
> So if you want to get involved with something that you can pick up, 
> put down and which isn't too onerous this could be for you.
>
> Before we can set up testing of applications ( it's tracked on a 
> Ubuntu QA tracker and they call it package testing) we need to make 
> sure the tests we do have are up to date.
>
> You will need a few things:
>
>  1. an up to date iso to boot - you can run the test from a USB, a
>     virtual machine
>  2. something to write on
>  3. a web browser
>  4. an e-mail client
>  5. patience - we've not checked them for at a year
>
> You can grab the iso from 
> http://cdimage.ubuntu.com/xubuntu/daily-live/current - this url is 
> always the latest.
>
> Open your browser at 
> http://packages.qa.ubuntu.com/qatracker/milestones/377/builds/146768/testcases 
>
>
> You'll see a list of applications and packages there.
>
>  1. Pick something you fancy checking - Reply All to this mail telling
>     other people what you intend to test (we'd not want everyone to be
>     checking the same testcase)
>  2. Open your chosen testcase, then click the Detailed information on
>     the testcase button and make a note of the Testcase ID
>  3. Follow the testcase _exactly_ as it tells you
>  4. Make notes where something isn't working as the testcase expects -
>     this is a bug, a testcase bug. If necessary continue to the next
>     step as best you can ignoring the instruction if the application
>     no longer works as written
>  5. When you have completed checking your testcase and assuming that
>     you found no errors with it - let us know on the mailing list.
>
> That's a lot of words which basically mean - read the testcase, follow 
> it and note down where something is different.
>
> If you did find an issue with the testcase - report it to Launchpad. 
> This could be as simple as the testcase calls for a button called Next 
> but it's now called Continue, it could even be that the testcase 
> covers something the application does but isn't tested.
>
>  1. Open your browser at
>     https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
>  2. In the Summary box - please report it with something like this
>     syntax Testcase 1559 Catfish Fails To Open From Whiskermenu, 1559
>     being the ID you previously noted
>  3. Click Next - then regardless of any previous bugs it prompts you
>     with - Click No, I need to report a new bug
>  4. Using the notes you made while checking the testcase fill in your
>     further information
>  5. You can now if you wish tell us the bug number - but it's not
>     necessary as I am subscribed to Testcase Bugs
>
> If you have needed to report a bug - the Testcase ID is important - 
> there are 1700 different ID numbers - and the majority refer to live 
> testcases.
>
> If the list of applications on the package tracker doesn't include 
> something you use that you think should be tested - and is something 
> that we have _by default_ - you can report this to the same url above 
> - just say Testcase need for 'you fave application we don't test'
>
> If I need further information I will comment on your bug report so 
> please keep an eye out for that.
>
> If you found that easy to do - how about doing another one ;)
>
> Cheers
>
> Kev
>
> for the Xubuntu Developers and QA Teams
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/xubuntu-devel/attachments/20180518/252eae94/attachment.html>


More information about the xubuntu-devel mailing list