Test Script Writing Guidelines

1
Test Script Writing Guidelines
Why Test Script ?
About Test Script
Guidelines For Test Script Writing
Check points for Test Script
Examples of Test Cases
2
What is Test Script
The term test script is the combination of a
test case, test procedure, and test data.
A test case is a document that describes an
input, action, or event and an expected response,
to determine if a feature of an application is
working correctly. A test case should contain
particulars such as test case identifier, test
case name, objective, test conditions/setup,
input data requirements, steps, and expected
results.
3
About Test Script
To increase the maintainability and re-usability
of your test scripts, they should have been
structured before they are implemented. A goal
should be to identify these actions so that you
can reuse their implementation.
4
Guidelines For Test Script writing

• Be concise with your wording
• Make the steps easy to follow
• Be descriptive if necessary
• Have a clear set of expected results
• Write your test cases so someone
  unfamiliar could understand them
• The optimum test case is one with the
  highest chance of detecting an
  error.
• Prepare test cases for invalid and
  unexpected situations as well as valid
  and expected ones.

Tip Use the Traceability Matrix to cross
reference the requirements to the test cases to
ensure each requirement is addressed. Add a
column to a copy of the matrix and identify the
test case for each requirement by number or name.
Complete the matrix as test cases are created.
5
Check Points
1) Does the test script have a unique name that
identifies the condition that the script
evaluates?  
2) Does the test script conform to the related
test case? Does the test script identify the test
case or cases that it implements? Ensure that
the test script conforms to the specification
established in the test case. The test case
captures the logical conditions of satisfaction
for test, and the test script must implement this
intent.   
3) Is the test script prescriptive and
unambiguous?   Does the test script have
clear pass or fail criteria? (Is it binary?)
Does the script use a request-response style in
its steps? (Is it procedural?) Does each
specific input have a specific expected result?
(Is it declarative?)
4) Is all required data specified? Ensure that
the test script contains or references all of the
test data required to actually run the script.
5) Is each post-condition of the related test
case evaluated by a step in the test script?
6
Check Points
6) Does the test script set up and tear down
appropriately? Does the test script identify the
preconditions that must be true before the test
script starts? Does the test script restore the
system's state after it runs, regardless of
whether it passes or fails? Can the test script
be executed without affecting the results of
other test scripts? In other words, can the test
script be run in any sequence? If not, is the
sequence dependency identified? The dependency
might be identified in the test script, in a
test suite, or in some other manner (such as by
using a test tool).
7
Examples
A) Test cases for biggest of three numbers 1) 1gt
999 valid 2) 9999 invalid 3) 99
invalid 4) 009 invalid ( as it is same as
9)? 5) space invalid 6) alphabets / special
characters invalid 7) negative number
invalid 8) decimals invalid Like this we can
add many more test cases depending on the
Specifications or Requirements document.
B) what are the sanity test cases for a water
Bottle? Check if the water bottle has a single
hole on the top to fill water in it.