ManualStyleGuide

Differences between revisions 4 and 5
Revision 4 as of 2013-02-22 15:46:13
Size: 1386
Editor: adsl-74-179-121-184
Comment:
Revision 5 as of 2013-02-22 15:47:59
Size: 1469
Editor: adsl-74-179-121-184
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * Make sure your testcase follows the [[https://wiki.ubuntu.com/Testing/TestCaseFormat#contribute|proper format]]. Notice the standard footer at the end as well. Be sure your testcase has this same footer.  * Make sure your testcase follows the [[https://wiki.ubuntu.com/Testing/TestCaseFormat#contribute|proper format]]. Notice the standard footer ('if all actions ...' or 'if you answer 'yes' to all ...') at the end as well. Be sure your testcase has the appropriate footer for your testcase.

This is a general style guide to how manual tests should be written.

Testcase Format

  • Make sure your testcase follows the proper format. Notice the standard footer ('if all actions ...' or 'if you answer 'yes' to all ...') at the end as well. Be sure your testcase has the appropriate footer for your testcase.

Testcase Wording

  • Write your testcase in English
  • Keep your testcase desktop and flavor agnostic. Whenever possible, don't force or assume a specific desktop in your testcase. The exception to this would be desktop specific testcases (such as the tests for Unity, Gnome, KDE etc.)
  • Ensure your testcase when possible doesn't require a specific locale. For example, the /home/username/Downloads folder is not name ~/Downloads in a non-english locale.

Testcase Naming

  • When contributing a new testcase:
    • Place it into the proper folder
    • Name it whatever you wish, disregarding the prefixed number that you see on other testcase names, ie 1420_Gedit Tests. Instead simply name yours PACKAGENAME Tests. Your new testcase will be assigned a number and renamed once it's uploaded to the testing tracker.

QATeam/ContributingTestcases/ManualStyleGuide (last edited 2013-06-11 21:55:59 by CPE-121-218-86-248)