Design

Test cases should be designed to exert transitions between states. A test case may exercise any number of transitions.

For every test case these should be clarified:

  • the starting state of the component;
  • the input to the component;
  • the expected outputs from the component;
  • the expected final state.

For every expected transition within a test case these should be clarified:

  • the beginning state;
  • the event which is the reason of transition to the next state;
  • the expected event which is the reason of transition;
  • the expected next state.

Test cases are designed to exert valid transitions between states.

Black-Box-Test-Techniques.-State-Transition-Testing

Analysis

State transition testing uses such model of the states the component may occupy, the transitions between states, the events which is the reason of transition, and the acts which can be the outcome of such transitions.

This model should include states, events, transitions, acts and their interrelation. The states of this model should be disjoint, identifiable and limited in quantity. Events which are the reason of transitions between states, and transitions may return to the state from which they started. The reason of events will be the inputs to the component, and acts in the state transition model may be the reason of the outputs from the component. The model will characteristically be represented as a state transition diagram, state table, or a state transition model.


http://qatestlab.com/

Share
Related Documents
  1. In What Stage Are There More Software Bugs? (2410)
  2. Basics of Software Testing Policy (2792)
  3. What Does Testing Company Need From User To Start Proper Testing? (2351)
  4. Start Software Testing On Early Stages. How Does This Affect Cost? (3292)
  5. Principal Types of Verification (2486)
  6. Latent and Masked Software Bugs. What Is The Difference? (2770)
  7. Main Types of Defects in Software Testing (3498)
  8. Successful Bug Reporting (2468)
  9. Software Testing Documentation (2580)
  10. White Box Test Techniques. Linear Code Sequence and Jump Testing (3281)
  11. Control, Monitoring and Estimation in Software Testing (2654)
  12. The Main Goal of Acceptance Testing (2987)
  13. Undesirable Bug Reporting (2271)
  14. Configuration Management in Software Testing (2649)
  15. Workbench Concept in Software Testing (2576)
  16. What Is Software Bug Seeding? (1327)
  17. What Is Data-Driven Testing? (2582)
  18. What Is The Difference Between White Box, Black Box And Gray Box Testing? (1396)
  19. Validation and Failures In Software Testing (3028)
  20. What to Test and What Type of Faults Are Found? (1969)