Calendar:QA TestCase Writing Day: Difference between revisions

Calendar:QA TestCase Writing Day (view source)

69 bytes added , 3 August 2006

Confirmed users

3,816

edits

@@ Line 35: / Line 35: @@
 # Highlight the "SECOND_STEP" text and type in the instructions for the second step, for example: "Give it a name with an apostrophe: Don's Calendar"
 # Add more numbers and steps as needed.
-** If the lines are long and wrap, don't worry about it.
+## If the lines are long and wrap, don't worry about it.
 # Replace "FIRST_EXPECTED_RESULT" with the first thing the program ''should'' do. For example: "Calendar is created"
 # Replace "SECOND_EXPECTED_RESULT" with the next thing the program ''should'' do. For example, "The choosen color is associated with the calendar"
-# Add in more \*'s and text as needed.
+# Add in more *'s and text as needed.
-# Replace PRODUCT with either "Lightning" or "Sunbird" to indicate which product you are writing the test for. If you know the test will apply to both products, put "Both" there.
+# Replace PRODUCT with either "Lightning" or "Sunbird" to indicate which product you are writing the test for. If you know the test will apply to both products, put "Both" there. (You can also just use a "L", "S", or "B" if you get tired of typing).
 # If the testcase you are writing stems from an existing bugzilla bug (and you know the ID), then fill in the Regression ID. It is an optional field. Not all test cases will have bugzilla ID's.
 ==Tips on Writing a Good TestCase==