What is a manual testcase?
Manual Testcases are simply sets of instructions designed to be followed and reported against by real people. These testcases can be more complex or require thought than an automated testcase and in general are easier to write. The quality team maintains a project repository for manual testcases.
Writing a manual testcase
STEP 1: Choose an application
Choose an application you wish to write the testcase for. Here’s a list of needed testcases that you can choose from. Branch the current testcases by issuing bzr branch lp:ubuntu-manual-tests.
STEP 2: Write the test
Run the application you’ve chosen and pick a few of the primary features of the application. Document each feature you’ve chosen and write down step by step instructions in order to utilize the feature. For example, if I want to ensure the bookmark manager in firefox works properly, I would write tests to test the ability to open, save, delete, edit and order a bookmark. These step by step instructions will become your action steps in the testcase.
TIP: Take a look at the current manual testcases located inside the folders you branched. Notice the formatting and the action followed by expected result format, and notice the html markup of dd and dt used. Your testcase should use this html formatting as well
Now, run through the steps you wrote down to ensure they exercise the feature you targeted. As you step through your instructions, record what happens for each step so you can add them to the test case. These will become your expected results in the testcase. For example, If I press Ctrl+o while in gedit, the expected result might be that a open window will appear.
Format your testcase steps and expected results in the proper testcase format. You should utilize the ‘normal’ testcase format where each step represents and ‘action’, followed by an ‘expected result’. Note that you have to use the html markup as shown. The tracker will interpert the html to display and number your items properly.
STEP 3: Contribute your new test!
I want to help, but I got lost somewhere!
I’d encourage you to visit our wiki pages on contributing testcases for more in-depth instructions and help. In addition, let us know about your work! Send an email to the QA Community Coordinator and/or the mailing list, email@example.com. They are happy to help you!
What does a testcase look like?
What testcases need to be written?
Testcases for any image, package, or potential piece of hardware that runs on ubuntu is welcome! If you are looking for ideas, here’s a list of needed testcases that you can choose from. Pick an item from the list and and have at it!
How do I contribute a manual test?
Contributions can be submitted by branching the code, bzr branch lp:ubuntu-manual-tests, pushing your new testcase to your own branch on launchpad and submitting merge requests containing the new testcase.
What happens to my contribution?
Once your new case has been accepted and merge, it will enter the pool of testcases available for usage on the various qatrackers. From there it can be utilized for all sorts of manual testing events; a special call for testing or as part of the normal cadence testing that occurs throughout the cycle.
Things you need to know:
The QATracker is the master repository for all our our testing within ubuntu QA. It holds our testcases, records our results, and helps coordinate our testing events. Learn more about it here.