Calendar:QA TestCase Writing Day: Difference between revisions

Jump to navigation Jump to search

Calendar:QA TestCase Writing Day (view source)

Revision as of 21:55, 3 August 2006

2,067 bytes added ,  3 August 2006
no edit summary
No edit summary
Line 2: Line 2:
Thank you for helping with our Test Case Writing Day. In order for our [[Calendar:TestDays]] to work, we need to create test cases. We appreciate your support.
Thank you for helping with our Test Case Writing Day. In order for our [[Calendar:TestDays]] to work, we need to create test cases. We appreciate your support.


==Where do I start?==
==What if I've Never Written a Test Case==
Don't worry. It is very easy. Just log into the IRC channel and we'll walk you through it.
 
==Getting into the IRC Channel==
* Go to your [http://www.ircreviews.org/clients/ favorite IRC client]:  
* Go to your [http://www.ircreviews.org/clients/ favorite IRC client]:  
** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
Line 14: Line 17:
==I'm in the Channel, now what?==
==I'm in the Channel, now what?==
Let the moderators (ctalbert, jminta, dmose) know if you have any questions or problems.
Let the moderators (ctalbert, jminta, dmose) know if you have any questions or problems.
==Create a Mozilla Wiki Login==


==Writing a TestCase==
==Writing a TestCase==
# Perform the steps to test in the product (either Lightning or Sunbird)
# Go to http://wiki.mozilla.org/Calendar:Test_Case_List
# Pick the subgroup of your testcase -- if you don't know where it belongs, ask in the IRC channel.
# Edit the section for that subgroup (you may have to log in to the wiki here)
# Copy the Template at the top of the section and paste it at the bottom of that section
# Replace the text in all caps with your text. For questions about the template see below.
==How to Edit the Template==
# Highlight "TESTCASE_SUMMARY" replace it with a one line description of your test case, such as "Create Local Calendar with apostrophe"
# Highlight the "FIRST_STEP" text and type in the instructions for the first step of the testcase, for example: "Launch New Calendar Dialog"
# 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.
# 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.
# 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.
# 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.




==How to Write a TestCase==
==Tips on Writing a Good TestCase==
1. Assume the person testing
* Pretend you're writing a bug - it's pretty much the same
* How to write a testcase *
* Assume that the person following your test case only has basic familiarity with the product. For example:
It's actually just like writing a bug.
** ''Bring up the New Calendar Wizard'' - This is not that good.
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"
** ''Launch the New Calendar Dialog (by either double clicking calendar list, File->New Calendar or right clicking calendar list).'' - This is much better.
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
* Be fairly specific with the expected results
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.
** ''It worked''  - This is very bad
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.
** ''The event was created on the proper day; The event had the proper color'' - This is very good
* Keep list of steps and expected results as simple as possible.
* You don't need to detail every click unless it's an important part of the testcase.
** ''Click on the name text box; enter a name. Click on Color drop down, pick red.''-- This is a little much
** ''Give the calendar a name, assign it a color.'' --This is much better.
Ctalbert
Confirmed users
3,816

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/30628"

Navigation menu