State Transition Testing Technique Training

software of a component or system.

What is dynamic testing?

What is

Black box testing: Method of testing that examines the functionality of an application without peering into its internal logical structure.

system where user gets a different output for the same

What is state transition testing?

State transition technique is a dynamic black-box testing technique, which is used when the system is defined in terms of states and the transitions between the states is governed by the rules of the system.

to visualize all of the states in which the system

- to capture certain kinds of system requirements and to document internal system design;

- can serve as a guide to creating test cases;

- is used in cases when system’s reaction depends on its state.

transitions (from one state to another)
- events (that cause

Actions that result from a transition are not shown explicitly but they would be a message to the customer saying things (such as 'Please enter your PIN').

Technique: designations

A state transition model can be represented as diagram and as a table.

account. He has 3 tries to enter valid PIN and

Wait for PIN

2nd try

3rd try

Access to account

Eat card

Start

Card inserted

Enter valid PIN

Enter invalid PIN

Enter valid PIN

Enter invalid PIN

Enter valid PIN

Enter invalid PIN

Technique: State diagram

In 10 seconds

card
Start
Card inserted
Enter valid PIN
Enter invalid PIN
Enter valid PIN
Enter
invalid PIN
Enter

Enter invalid PIN

Card inserted

Card inserted

Enter invalid PIN

Enter valid PIN

Technique: State diagram

In 10 seconds

Card inserted

Enter valid PIN

Enter valid PIN

Enter invalid PIN

Enter valid PIN

transition table.
Where every column illustrates every transition from one state

Technique: State table

where the correct PIN is entered the first time.
Wait

2nd try

3rd try

Access to account

Eat card

Start

Enter valid PIN

Enter invalid PIN

Enter valid PIN

Enter valid PIN

Enter invalid PIN

Card inserted

Technique: Test Cases. 1st flow

Enter invalid PIN

In 10 seconds

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Test

Enter invalid PIN

A second test (to visit every state) would be to enter an incorrect PIN each time, so that the system eats the card.

In 10 seconds

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Cover

Enter invalid PIN

In 10 seconds

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Test

A third test case where the PIN was incorrect the first time but OK the second time.

In 10 seconds

Enter valid PIN

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Cover

In 10 seconds

Enter valid PIN

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Test

A fourth test where the PIN was correct on the third try.

In 10 seconds

Enter valid PIN

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Cover

A fourth test where the PIN was correct on the third try.

In 10 seconds

Enter valid PIN

PIN
Enter invalid PIN
Enter valid PIN
Enter valid PIN
Enter invalid PIN
Technique: Cover

Enter invalid PIN

In 10 seconds

PIN
2nd try
3rd try
Access to account
Eat card
Start
Card inserted
Enter valid PIN
Enter invalid

Enter valid PIN

Enter invalid PIN

Enter valid PIN

Enter invalid PIN

Card inserted

Card inserted

Card inserted

Enter invalid PIN

Enter valid PIN

Enter valid PIN

Technique: Test Cases. Another flow

Enter invalid PIN

In 10 seconds

than once and leads to the same state there is

Technique: simplistic diagram

Wait for PIN

2nd try

Enter invalid
PIN
try = 1

or

Enter invalid
PIN
try = 2

nth try

Enter invalid
PIN
try = n-1

Wait for PIN

Enter invalid PIN
try = 1

Enter invalid PIN
try = 2

Enter invalid PIN
try = n-1

Wait for PIN

…

Eat card

Enter invalid
PIN
try = n

Enter invalid PIN
try < n

Enter invalid PIN
try = n

Enter invalid PIN
try = n

or

PIN
Technique: simplistic diagram
We can consider the repeated events as a

Enter invalid PIN,
try < 3

In 10 seconds

Access to account

with equal behavior can be considered as one event.
Enter invalid

~ Enter invalid PIN (try = 3)

~ Enter invalid PIN (try > 3)

~ Enter invalid PIN (try = n)

where the correct PIN is entered the first time.
Technique:

Wait for PIN

Eat card

Start

Card inserted

Enter invalid PIN,
try =3

Enter valid PIN

Access to account

Enter invalid PIN,
try <3

In 10 seconds

every state) would be to enter an incorrect PIN each

Wait for PIN

Eat card

Start

Card inserted

Enter invalid PIN,
try =3

Enter valid PIN

Access to account

Enter invalid PIN,
try <3

In 10 seconds

the PIN was correct the second or third time.
Wait for

Eat card

Start

Card inserted

Enter invalid PIN,
try = 3

Enter valid PIN

Access to account

Enter invalid PIN,
try < 3

In 10 seconds

of money he likes to send, types mobile number and

Example 1

and phone number


Valid sum and phone number
Invalid sum and /

The money has been sent

repeat the operation of entering sum and phone number.
Example 1:

Start

Validation phone number and sum

Enter sum and phone number

Invalid sum or phone number

This issue should be clarified with BA.

We should find the cases when it has sense.

project);
It depends on:
- Cost of mistake.
- Time constraints;
- Budget constraints;
-

- Business need;

- Quality requirements for the project from customer;

sum and phone number


Valid sum or phone number
Invalid sum or

The money has been sent

Start

A first test case here would be the normal situation, where the correct sum and phone number are entered the first time.

A first test case here would be the normal situation, where the correct sum and phone number are entered the first time.

visit every state) would be to enter an incorrect sum

Validation phone number

Send money

Enter sum and phone number

Valid sum or phone number

Invalid sum or phone number

The money has been sent

Start

visit every state) would be to enter an incorrect sum

Validation phone number

Send money

Enter sum and phone number

Valid sum or phone number

Invalid sum or phone number

Start

The money has been sent

chocolate (e.g. ‘KitKat’), and enters money. If not enough money

Example 2

for enough money
Start
Enter money
Enter
money
Select type of chocolate
Not enough

Money back

Give chocola-te

Enough money, with or w/o change

Chocolate exists

In 10 seconds

In 10 seconds

Chocolate doesn’t exist

money
In examples we should discover how much times user has

This issue should be clarified with BA.

We should find the cases when it has sense.

minimum number of cases we should make for sum validation?

Example 2: Notification 1

Every bank notes and coins? - until get the ___________________________chocolate cost.

10? - equal the chocolate cost;

20? - more the chocolate cost;

1cop? - until get the chocolate cost;

repeat the operation of chocolate (the number of types chocolate,

Example 2: Notification 2

Start

Check selected chocolate

Select type of chocolate

Chocolate doesn’t exist

This issue should be clarified with BA.

We should find the cases when it has sense.

project);
It depends on:
- Cost of mistake.
- Time constraints;
- Budget constraints;
-

- Business need;

- Quality requirements for the project from customer;

would be the normal situation, where the enough sum of

Type of chocola-te

Valida-tion sum

Check selected chocola-te

Wait for enough money

Start

Enter money

Enter
money

Select type of chocolate

Not enough
money

Money back

Give chocola-te

Enough money, with or w/o change

Chocolate
exists

In 10
seconds

In 10 seconds

Chocolate doesn’t exist

to enter not enough sum of money the first time,

Type of chocola-te

Valida-tion sum

Check selected chocola-te

Wait for enough money

Start

Enter money

Enter
money

Select type of chocolate

Not enough
money

Money back

Give chocola-te

Enough money, with or w/o change

Chocolate
exists

In 10 seconds

Chocolate doesn’t
exist

In 10
seconds

transitions.
These flows are used to create main test cases.

But

Additional test cases may make you feel warm and fuzzy. But there’s less probability that they discover defects previous cases don't find.

the enough sum of money is entered the first time,

Type of chocola-te

Valida-tion sum

Check selected chocolate

Wait for enough money

Start

Enter money

Enter
money

Select type of chocolate

Not enough
money

Money back

Give chocola-te

Enough money, with or w/o change

Chocolate
exists

In 10
seconds

In 10 seconds

Chocolate doesn’t exist

to enter not enough sum of money the first time,

Type of chocola-te

Valida-tion sum

Check selected chocola-te

Wait for enough money

Start

Enter money

Enter
money

Select type of chocolate

Not enough
money

Money back

Give chocola-te

Enough money, with or w/o change

Chocolate
exists

In 10 seconds

Chocolate doesn’t
exist

In 10
seconds

the state of the application may vary.
Determine all the events

So State Transition testing technique is a tool to:

all states.
Consider and prioritize according to requirements all ways which

Identify all transitions.

Create a test case for each way, that covers main functionality.

Create additional test cases that cover remaining functionality (if it is needed).

Short Name (SN).

If the SN was entered incorrectly the warning

Task 1

and time
Appointment is created
Start
Select the date
Select Op and time
Wait

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

would be the normal situation, where the SN was entered

Validati-on of SN and date

Wait for Op and time

Appointment is created

Start

Select the date

Select Op and time

Wait for SN

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

the case when some of validation doesn’t pass every time.

Validati-on of SN and date

Wait for Op and time

Appointment is created

Start

Select the date

Select Op and time

Wait for SN

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

the SN is invalid at first time but valid at

Validati-on of SN and date

Wait for Op and time

Appointment is created

Start

Select the date

Select Op and time

Wait for SN

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

the SN is valid at every time and the provider

Validati-on of SN and date

Wait for Op and time

Appointment is created

Start

Select the date

Select Op and time

Wait for SN

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

At first time SN is invalid at but valid at

Validati-on of SN and date

Wait for Op and time

Appointment is created

Start

Select the date

Select Op and time

Wait for SN

Enter SN

Invalid SN

Provider is busy

SN is valid and provider isn’t busy

the list of clinic's providers and than enters the date

Task 2

Provider can entre invalid date twice. After third invalid try the calendar with available dates for selected provider appears. And the date should be selected from calendar.

If selected operatory is not available the appropriate message appears and provider should select another operatory (Op) from appeared list of free operatories.

time
Validati-on of Op
Start
Select Op
and time
Wait for date
Select SN
Select

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try = 3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

would be the normal situation, when the date was entered

Op and time
Validati-on of Op
Start
Select Op
and time
Wait for date

Select SN

Select date

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try = 3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

The date is invalid at every time and provider is

Op and time
Validati-on of Op
Start
Select Op
and time
Wait for date

Select SN

Select date

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try = 3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

the date was entered incorrectly and provider is busy at

Op and time
Validati-on of Op
Start
Select Op
and time
Wait for date

Select SN

Select date

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try = 3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

the date was entered incorrectly and provider is busy every

Op and time
Validati-on of OP
Start
Select Op
and time
Wait for date

Select SN

Select date

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try=3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

the date was entered correctly and provider is not busy

Op and time
Validati-on of Op
Start
Select Op
and time
Wait for date

Select SN

Select date

Provider is busy or incorrect date format
Try < 3

Provider isn’t busy

Enter the date

Provider is busy or incorrect date format. Try = 3

Calendar

Appoint-ment is created

List of free Ops

Op is available

Op isn’t available

Select Op

adds planned Proc to the patient;
2. When planned Proc has

4. If planned or completed Proc has incorrect information and it has not been paid yet it can be deleted by provider;
5. If 100 days take after adding planned Proc it will automatically become inactive and can't be deleted, but it can be voided by provider;
6. If 100 days take after adding complete Proc, that has not been paid it will auto-matically get status 'Warning‘ and can't be deleted, but it can be voided or paid;
7. It is no possibility to make any operation with paid Proc.

‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose ‘Void’
status
Warning

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status

would be the normal situation, when planned procedure for selected

Proc
Delete Proc
Complet-ed
Proc
Choose ‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose ‘Void’

Warning Proc

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status

the planned procedure has been added, completed, deleted, and than

Proc
Delete Proc
Complet-ed
Proc
Choose ‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose ‘Void’

Warning Proc

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status

the planned procedure has been added, and voided after 100

Plan’
Proc
Delete Proc
Complet-ed
Proc
Choose ‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose

Warning Proc

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status

the planned procedure has been added completed, after 100 days

Plan’
Proc
Delete Proc
Complet-ed
Proc
Choose ‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose

Warning Proc

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status

the planned procedure has been added completed, after 100 days

Plan’
Proc
Delete Proc
Complet-ed
Proc
Choose ‘Completed’ status
Delete Proc
Choose ‘Paid’ status
In 100 days
Voided
Choose

Warning Proc

In 100 days

Patient selected

Choose ‘Paid’ status

Choose ‘Void’ Status