Testing artifacts test cases

Software Testing Fundamentals

Module 1: Introduction into Software Testing

Software Testing Artifacts


Test Cases

2 ® 2011. EPAM Systems. All rights reserved.

Software Testing Definition
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.


Conclusion
1. Start with obvious and simple tests. Test the program
with easy-to-pass values that will be taken as serious issues
if the program fails.
2. Look for more powerful tests. How to break it? Once
the program can survive the easy tests, put on your thinking
cap and look systematically for challenges.
3. Pick boundary conditions. There will be too many good
tests.You need a strategy for picking and choosing.
4. Do some exploratory testing. Run new tests every week,
from the first week to the last week of the project.
5. Learn from experience.



Writing Down Test Cases


Writing Down Test Cases
 Introduction into Test Cases
 What is it?
 Why do we need them?
 Templates to use
 Writing Good Tests Cases
 Test scenarios


Test Case: What is it?
IEEE Standard 610 (1990) defines test case as follows:
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.

(IEEE Std 829-1983) - Documentation specifying inputs, predicted
results, and a set of execution conditions for a test item.


Test Cases: Why do we need them?
 Why should we spend time writing our tests down?
 We could run so many tests instead!

With test cases we can:
• Plan, only then run -> structured and systematic approach-> less
bugs missed (!)
• Store information
• Test the Requirements documentation before application is available
• Accelerate regression testing
• Pass information to new members of the team
• Remember ourselves what tests we„ve designed half a year ago
• Reuse “checklists” between projects
• Track testing progress (X% tests executed,Y% tests passed (failed),
Z% requirements covered)



Relationship of Test Documents to Testing Process


Functional Testing Workflow
Software Testing Stages

Test Test
Designing Executing

Test Analyze &
Planning Reporting
Initiation

Completion


Relationship of Test
Documents to
Testing Process
Test Plan

Test Specification

Test Design Specification
Test Case Specification
Test Procedure Specification

Test Reporting

Test Item Transmittal Report
Test Log
Test Incident Report
Test Summary Report



Test Specification



Test Specification – IEEE 829


Test Specification IEEE829

Test Design Specification


Test Procedure Specification

Test Design Specification
Purpose
To specify refinements of the test approach and to identify the
features to be tested by this design and its associated tests.

Outline
a) Test design specification identifier;
b) Features to be tested;
c) Approach refinements;
d) Test identification;
e) Feature pass/fail criteria.


Purpose
To define a test case identified by a test design specification.

Outline
a) Test case specification identifier;
b) Test items;
c) Input specifications;
d) Output specifications;
e) Environmental needs;
f) Special procedural requirements;
g) Intercase dependencies.


Test Procedure Specification
Purpose
To specify the steps for executing a set of test cases or, more
generally, the steps used to analyze a software item in order to
evaluate a set of features.

Outline
a) Test procedure specification identifier.
b) Purpose;
c) Special requirements;
d) Procedure steps.



Test Specification – EPAM


Test Case Anatomy
 We want to document a test. What information should
we record?
 Steps
 Expected results
 Passed or failed
 Title
 Some ID
 Related requirement
 Priority (Smoke, Critical, Extended; or A, B, C, D or any
other)
 Module, submodule
 Initial data we need for test
 Author, last time run, actual result, related bug


EPAM Testthat is
Priority Requirement Case: Title – summary what
Excel Template result
Expected
(low) tested we are testing after each step

ARC_ L R25 Save Upload Upload, file name with 1. Upload dialog appears Not
C10.1 item file special symbols 2. Browser's "choose file" tested
95 Setup: On your computer dialog appears
create file named `~!$^()- 3. "choose file" dialog
Test _+[]{}',.html , not empty closes, `~!$^()- Status in the
Case ID 1. Click Upload button _+[]{}',..html appears in
build
Setup
2. Click Browse button the FROM field. (passed/failed/no
3. Select `~!$^()- 4. Upload dialog closes,
t tested)
_+[]{}',..html file and click file name from the TO
Open. field is substituted in the
Module and 4. Click upload long description file name
Submodule 5. Click Add To List field. File contents is
shown below.
5. Attachment is added

Steps to perform

Test Scenarios (Test Suite)

 Test scenario = a set of test cases for some purpose.

 Good test scenario flows along some logic - typical usage,
convenience to test, by modules.


Writing Test Scenarios

 Choose a part, use grouping.
 Write Smoke and Critical scenarios.
 Move from simple tests to more complex.
 Organize scenarios logically (do not use test cases from other
parts, scenario should be convenient to pass).


EPAM Test Cases Template
Title page
Smoke test page
Excel Groups by
features

Author(s)

Pages for Smoke,
Critical, Extended test
levels Automatic
History of changes
Statistics

Last changes are
Legend
marked in blue

Test Scenarios in PMC
Run Scenario

Scenarios

Test Cases

Test cases list
Run Test
Case


Writing Test scenarios… continuation
 One test for one check.
 Titles reveal the main point of tests.
 Preparation (initial data, that can be used while
passing the scenario).
 Do not repeat exact steps to achieve the same result
(can be given in the first test only).
 Alternate cases giving one result with cases giving
another.


Several tricks to write test cases
 Copy-paste.
 Write questions right into test case and mark with a color: if
you still have question on any requirement and you cannot
write a test case definitely, you can mark the issue with red
and write comments.
 Use several colors to mark new (just added), old test cases,
test cases with questions.
 Cases should have a good logical structure: use Excel grouping.
 Create a history for the file with test cases.



How To Create Good Test Case?


Good Test Case: Conclusion
An excellent test case satisfies the following criteria:
 Reasonable probability of catching an error.
 Exercises an area of interest.
 Does interesting things.
 Doesn‟t do unnecessary things.
 Neither too simple nor too complex.
 Not redundant with other tests.
 Makes failures obvious.
 Allows isolation and identification of errors.

What else?


Steps to Create Test Cases
1. Start early – before the first build.
2. Break application into functions/modules to be
tested.
3. Write checklist for each function/area.
4. Add any questions, as you go.
5. Fill in details, resolve questions.
6. Add cosmetics – for better reading.
7. Get review from other tester, developer, customer.
8. Update as soon as mistake is found.
9. Update as functionality changes.

Step 1
Start early- before the first build

What sources of information do we have at this time?
What sources do we not have?

You cannot see working application.
Learn all sources of information you have, first (documents,
people, etc).
Your questions may find and correct serious holes in design.
Test cases creation goes parallel with requirements review.

You cannot predict all bugs.
Design still may change.

Step 2
Break application into functions/modules to be tested

Break into pieces
until each piece is simple enough
to list all tests


Step 3
Write checklist for each function/area.

Easy to check that all tests included.
Easy to reorder.
Easy to see where to use copy-paste.
We separate 2 different kinds of work (thinking and writing).

Do not just copy requirements into cells.
1 line=1 test case.
If something is not clear – write a question right NOW.


Steps 4,5,6
Add any questions, as you go.
Fill in details, resolve questions.
Add cosmetics – for better reading.

Then use copy paste.


Step 7
Get review from other tester, developer, customer.

 Are some interesting tests missed?
 Are some tests redundant?
 Are test cases easy to understand by other person? Novice
tester?
 Is it what customer expects?
 Are there any errors? (there is always at least one more )


Step 7
Get review from other tester, developer, customer.

 Another point of view (developer, marketing).
 It‟s hard to notice your own mistakes.
 Often we do not have some information.
 Developer can have another opinion; we can clarify before the
code is created.
 Often getting review is not easy, but if done thoroughly, it is
very useful.
 Raises standard for test cases.


Steps 8,9
Update as soon as mistake is found
Update as functionality changes

 Small corrections: do right now, until you forget!

 Big changes – you can find time for them:
• At the beginning new phase.
• At the end of a build cycle.
• Sudden free time due to build delay, etc.


Your Global Technology Outsourcing Partner

Thanks for your attention

EPAM Systems, Inc.
http://www.epam.com

NTUU “KPI”
EPAM POWER POINT TITLE
http://kpi.ua
Sub Topic

® 2011. EPAM Systems. All rights reserved.

Testing artifacts test cases

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Testing artifacts test cases (20)

Recently uploaded (20)

Testing artifacts test cases