The document discusses test case structure and specifications. It defines a test case as a set of inputs, expected results, and execution conditions used to test a specific program path or requirement. A test case specification is a document that specifies test cases by outlining objectives, inputs, test actions, expected results, and preconditions. It also provides guidelines for writing effective test cases, such as keeping them short, using simple language, and providing test data and notes when possible. The overall goal is to write test cases early based on design to allow for early bug detection and efficient testing once code is completed.

1. Test Case

2. Test Analysis
Test Design Techniques
Selection
Test Design
Specification
Test Case Specification
Test Plan
SRS
Mock-ups
Test Design
Specification
…
Test Case
Specification
Trainings’ Content

3. What is Test Case?
 Test case is:
– a set of input values, execution preconditions, expected results and
execution, post conditions, developed for a particular objective or
test condition, such as to exercise a particular program path or to
verify compliance with a specific requirement
– documentation specifying inputs, predicted results, and a set of
execution conditions for a test item
according to Standard Glossary of Software Engineering (IEEE 610)

4. Test Case Structure
 Depending on the particular project Test Case might consists of:
Attachment
Test Case
Name
Description
/ Objective
Priority
Test Steps
Expected
Result
Test Inputs
/ Test Data
Actual
Result
Test Case
ID
Test Case
Type
Automation
Status
Pre-
condition
Execution
Result /
Status
Test Case
Structure

5. Requirements
Test Design
Test Case
Test Case Example

6. Test Case Example

7.  Test Case Specification – a document specifying a set of test cases
(objective, inputs, test actions, expected results, and execution preconditions) for a
test item (After IEEE-829)
 According to IEEE 829 Test Case Specification consists of:
1. Test case specification identifier
2. Test items
3. Input and Output specifications
4. Environmental needs
5. Special procedural requirements
6. Inter-case dependencies
Test Case Specification

8. Test Design & Test Case Specifications
Test Design Specifications Test Case Specifications
Objective To identify set of features
or combination of
features to be tested.
To specify in details each
test listed in Test Design
Specification.
Content The list of all tests, test
scenarios and checklists
that will be created for
testing of some feature
during particular testing
stage.
Only test cases.
Test Data Does not record the
values to be entered for a
test, but describes the
requirements for defining
those values.
Specifies test data for use
in running the test
conditions identified in
Test Design Specification.

9. Goals of writing Test Cases:
 Testing efficiency: the idea is to write test cases based on design
while code is incomplete, so that we could test product quickly
once the code is ready
 Early bug detection: errors in code can be prevented before the
coding is done, also new test ideas will be generated
 Test credibility: test cases are supposed part of the deliverable to
the customer
 Ability to cover all parts of the requirements
 Legal documents of testing work, in case information is needed
for law suits
 Ability to track history while iterations
 Usefulness while bringing in new testers
Goals

10.  Write short test cases (up to 10-15 steps)
 Use simple English and general words
 Write test cases to quick and easy to determine
the expected result
 Provide test data if possible
 Write in details SQL queries (it will save time while
executing)
 Add reference to bugs and requirements
 Add some notes in case you want to convey
additional information
 Highlight important things, marking them in bold
or assigning them color or writing in different font
Best Practices

11. Thank You!