Confirmed users
3,816
edits
Calendar:QA TestCase Writing Day: Difference between revisions
Jump to navigation
Jump to search
→How to Write a TestCase
| Line 20: | Line 20: | ||
==How to Write a TestCase== | ==How to Write a TestCase== | ||
1. Assume the person testing | 1. Assume the person testing | ||
* How to write a testcase * | |||
It's actually just like writing a bug. | |||
1. You come up with a test case summary - a one line description about the test case. For example, "Creating a Local Calendar with weird name" | |||
2. You List the steps that the tester must perform: Bring up New Calendar Wizard; Give it a name like 'Don's Crazy $#@%% Calendar'; Give it a color | |||
3. Next, you list what the program SHOULD do. These are the expected results. For example: The calendar is created; It is associated with the color you picked. | |||
4. If this test case has been submitted to bugzilla, you may enter a bugzilla ID number for it. This is optional. A testcase does not have to be associated with a regression ID. In fact, most are not. | |||