Testplace tutorials
  • Quality Assurance 101
  • Manual Testing
    • Manual Testing Tutorial
      • What is Software Testing?
      • Software Development Life Cycle
      • Software Testing Life Cycle
      • Types of Software Testing
      • Levels of Testing
      • Automation Vs Manual Testing
      • Black Box & White Box Testing
      • Smoke & Sanity Testing
      • Regression Testing
      • Retesting
      • Regression vs Retesting
      • Entry And Exit Criteria
      • Test Scenario vs Test Case
      • Manual Testing Methods
      • Verification and Validation
      • Test Strategy
      • Test Plan
      • Test Strategy vs Test Plan
      • Bug Report Template
      • Test metrics
      • Difference Between Defect Bug Error And Failure
      • Write Good Bug Report
      • Principles of Software Testing
      • Black Box Test Design Techniques
      • Equivalence Partitioning Testing Technique
      • Boundary Value Analysis Testing Technique
      • Decision Table Test Design Technique
      • State Transition Test Design Technique
      • Severity Vs Priority
Powered by GitBook
On this page

Was this helpful?

  1. Manual Testing
  2. Manual Testing Tutorial

State Transition Test Design Technique

PreviousDecision Table Test Design TechniqueNextSeverity Vs Priority

Last updated 5 years ago

Was this helpful?

Using state transition testing, we pick test cases from an application where we need to test different system transitions. We can apply this when an application gives a different output for the same input, depending on what has happened in the earlier state.

Some examples are Vending Machine, Traffic Lights.

Vending machine dispenses products when the proper combination of coins is deposited.

Traffic Lights will change sequence when cars are moving / waiting

Example on State Transition Test Case Design Technique:

Take an example of login page of an application which locks the user name after three wrong attempts of password.

A finite state system is often shown as a state diagram

It works like a truth table. First determine the states, input data and output data.

Entering correct password in the first attempt or second attempt or third attempt, user will be redirected to the home page (i.e., State – S4).

Entering incorrect correct password in the first attempt, a message will be displayed as try again and user will be redirected to state S2 for the second attempt.

Entering incorrect correct password in the second attempt, a message will be displayed as try again and user will be redirected to state S3 for the third attempt.

Entering incorrect correct password in the third attempt, user will be redirected to state S5 and a message will be displayed as “Account locked. Consult Administrator”.

Likewise, let’s see another example.

Withdrawal of money from ATM. ‘User A’ wants to withdraw 30,000 from ATM. Imagine he could take 10,000 per transaction and total balance available in the account is 25,000. In the first two attempts, he could withdraw money. Whereas in the third attempt, ATM shows a message as “Insufficient balance, contact Bank”. Same Action but due to change in the state, he couldn’t withdraw the money in the third transaction.