#13 How To Create A TestCase

Test Case Process
 Test Case: A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
 Test Script: scripts that use for testing or check the output or for automation testing
 Test Data: data is using for testing

Why Test Case?
 Detail of test design to describer how to deploy test design
 Predict expected result
 Help new testers familiar with existing application/system without reading requirement

Good Test Case
 Has a high probability of finding errors
 Clear of purpose
 Well organized
 Reviewable
 Maintainable
 Useful to other testers

Test Case Structure
 General information: cover sheet
 Project information
 Record of change
 GUI: List all screen information to check easily
 [Module Name] test cases
 Pictures: list all screen designs that should be tested.
These screens must be approved by customer
 Test Report Refer to Test Case template

GUI – Graphic User Interface
 Screen Name
 Field Name
 Expected Output:
 Type
 Mandatory
 Editable
 Default value
 Max Length
 Range Value
 Test Status
 Test Date
 Notes.

GUI -  example

[Module] Test Case
 ID
 Test case description:
 List cases/scenario that will be tested
 List cases, designed in test design document for the specific function/module
 Test case procedures:
 Test actions taken by the actor when executing a testcase
 Test input: the actual values/data input by the actor at each step/action
 Expected output: the expected response from the application for a given step/action
 Inter-test case dependence: List all test cases that must be done before performing this case
 Actual output: the actual response from the application for a given step/action
 Result: Pass; Fail; Untested; N/A
 Note

Test Script
 Check test output
 Recorded automatically
 Coded manually: using test tools or standard programming languages like VB, C/C++, Java or SQL
 Test stub: temporary implementation of part of a program for unit test purposes
 Test driver: program which sets up an environment to call a module (or function) for testing

Test Script [Example]
 Check test output
 Recorded automatically: using RUBY test tool