Web Contest Test Suite Example

From dis-Emi-A

Contents 1 Requirement 2 Flowchart 3 Input List / First Draft 4 Input List / Completion

Requirement

In this example we have received the requirements written in a simple bullet form.

• In order to generate interest in a new product we intend on offering a contest.
• The contest entry form will be a web form requesting basic demographic data as well as email address.
• Any user may only enter the contest once
• Upon registration the user will get a thank you screen and an email confirming their entry
• To aid in marketing, arrival at the contest form page will track the partner through which the user came

Flowchart

Based on these requirements we would come up with a simple flowchart as follows.

Note that the page "Already Entered Page" is implicit in the requirements: there is a transition mentioned, but not explicit reference to this page.

Input List / First Draft

In the first draft we'll simply list all of the inputs we know about at each transition.

(1)

• Partner
  • From the requirements we know that there was a partner who directed us to this form. This input variable is that partner.

(2)

• Email
  • explicitly mentioned in requirements
• First Name
  • assumed from demographic information, the whole software always uses the same fields
• Last Name
• Age
• Province

Input List / Completion

Now, using the details of Input_classification we will identify exactly where in the process all of this information comes from, and add any extra fields we may have missed.

(1)

• Partner - system immediate HiddenVariant
  • HiddenVariant since we assume this data comes from a hidden field, or the HTTP referal header

(2)

• Email - user immediate OpenVariant
  • These fields are user entered in the web form, and the user can likely enter whatever they want
• First Name - user immediate OpenVariant
• Last Name - user immediate OpenVariant
• Age - user immediate OpenVariant
• Province - user immediate OpenVariant