ManualStyleGuide

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2013-02-21 22:11:07 →
Size: 1106
Editor: adsl-74-179-121-184
Comment:
← Revision 2 as of 2013-02-22 02:56:22 → ⇥
Size: 1130
Editor: ip-109
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * Keep your testcase desktop and flavor agnostic. Whenever possible, don't force or assume a specific desktop in your testcase. Exceptions to this would be desktop specific testcases that test things specific  * 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.)

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

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
      • Hardware test (laptop.qa.ubuntu.com), place into a hardware folder
      • Image test (iso.qa.ubuntu.com), place into the image folder
      • Application test (packages.qa.ubuntu.com), place into the packages 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)