[ubuntu-studio-devel] Manual Test Cases

Ross Gammon retail at the-gammons.net
Sat Dec 5 14:09:34 UTC 2015


Hi All,

I have been meaning to write an update on our progress with the test cases.

Last weekend Bart volunteered out of the blue to help out and produced 2
test cases with the help of flocculant. Here is one of them:
http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/view/head:/testcases/packages/Studio/1665_inkscape

It ends up looking like this on the QA package tracker:
http://packages.qa.ubuntu.com/qatracker/testcases/1665/info

And this weekend it looks like Set is going to have a go at Sribus. Keep
it up guys!!!!

If you want to help out, here are some tips:
1. Here is the table with the list of needed test cases:
https://wiki.ubuntu.com/UbuntuStudio/Testing/Testcases

2. Here is the guidance on the process:
https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual

Here is the rough flow (print it out for a checklist for your 2nd & 3rd
ones........):
-Assign yourself to the bug
-Create a local branch: bzr branch lp:ubuntu-manual-tests
-Make changes to the testcase in your local branch (or add a new file
with the name of package in the Studio folder)
-Commit the changes: bzr commit -m "Fix LP bug #BUGNO."
-Push to a personal remote branch: bzr push
lp:~username/ubuntu-manual-tests/bug-BUGNO
-Link the branch to the bug
-Propose the branch for merging and subscribe a reviewer to the bug
(flocculant is a good bet :-) )

You can stick to basic open, edit, & save operations if you prefer, or
go a bit deeper into scribus. The more testing we do, the more we are
sure that it will work when released. But if the testing takes longer
than 30 minutes, we have definitely gone too deep. It is better to aim
for about half that.

flocculant and I are standing by to help you through the process.

It is great to have a few people getting involved!!!

Cheers,

Ross



More information about the ubuntu-studio-devel mailing list