Good and Bad State Graphs in Software Testing Methodologies

A good or bad state graph is basically biased by the kind of state graphs that are likely to be utilized in the context of a software test design
Properties of good state graph
The total number of states is equal to the product of the possibilities of the factors that make up the stat
For every state and input, there is exactly one transition specified to exact one, possibly the same state
For every transition, one output action is specified. The output can be unimportant or does something sensible
For every state, there is a sequence of inputs that will drive the system back to the same state
In genereal, a state graph should have at least two different input codes
Two state graphs with same state, inputs and transitions can have different outputs. But, form the point of view of a state-testing, they might be identical
Bad State graphs contain inreachble states. Possiblity of reaching every state from every other state is zero, Also, it is not possible to reach start state form itself
The given image shows the example of improper state graphs

Share on Google Plus

About Data Sciences by Venu

Hi, My name is Venugopala Chary and I'm Currently working as Associate Professor in Reputed Engineerng College, Hyderabad. I have B.Tech and M.tech in regular from JNTU Hyderabad. I have 11 Years of Teaching Experience for both B.Tech and M.Tech Courses.
    Blogger Comment
    Facebook Comment

2 comments:

  1. GOOD MATERIAL FOR REFERENCE PURPOSE... IT HELPS FOR TESTER ALSO...

    Dr.S VENKATA ACHUTA RAO PH.D. CSE AI&ML

    ReplyDelete
  2. I have read your full blog, your content is so informative. Thanks for sharing valuable piece of content.
    The Future of Full Stack Development: Adapting to Changing Technological Landscape

    ReplyDelete