State Transition Diagram-State Transition Testing-State Transition Diagram In Software Testing

[@prateekmishra3508]

The most clear and concise tutorials. Tons of videos these days but you have managed to teach clear concepts 8 years back. I hope you are continuing uploading videos.

[@QA1]

@Prateek Mishra - Yes, I have continued uploading videos. Check out at kzbin.infovideos Many thanks for your encouraging words 🙏

[@prateekmishra3508]

i would suggest you maybe to promote your videos , this would help aspirant to search your videos easily.Just a suggestion!!

[@registerfor32]

great video. very clear and organized making it easy to understand. You are a life saver !

[@gacum1992]

Buay Deng gv. J

[@Aishwaryasaid]

Best Video...excellent explanation.....Thank u so much sir for this great video

[@vajjuramana123]

Thank you for the detailed video with explanation

[@WojciechWojciechowski]

Great tutorial ! Clear and nice :) I just have in mind one transition more to be added in car example - from constant speed to constand speed. For example , when we have constant speed and we keep gas pedal constant , we expect that car speed is more or less constant all the time.

[@QA1]

ederlezi123 Thank you for your comment. If it is possible for the system to transit from a state to the same state, there would be an arrow on that state circling back to itself. In the car example, it is possible for us to be in the constant speed state, accelerate/ brake and transition back to the constant speed state. Thanks again.

[@nataliianataliia2442]

Thank you for the explanation!

[@sajidzaheer9214]

excellent video, clearly elaborated, simple examples, very well done sir

[@QA1]

Sajid - many thanks for your kind words. Appreciate it.

[@deepak.nallapati6049]

Hi sir, Thanks for the video, Excellent explanation..I understood very clearly.

[@silentkiller4009]

Good video.Thank you very much!

[@TravellerI5]

Thanks, its very easy to hunderstand and very useful

[@erfanakhtarjahan7814]

Thank you for this detailed video. I'm planning to give the ISTQB Advanced Test Analyst exam soon and was wondering if you had any test examples that would cover the Specification-Based Testing Techniques? Thank you.

[@QA1]

Yes, Erfan. I have explained multiple examples in my specification-based test design techniques like Equivalence Classes, Boundary Value Analysis, Decision Tables etc. The link to these tutorials is kzbin.info/www/bejne/q6rHcqygprmGn9k

[@erfanakhtarjahan7814]

Thank you Sir.

[@pinky948]

Hello Sir, First of all thanks for very clear and neat explanation about concepts.All my confusion on concepts got cleared after seeing these videos of your tutorial.Sir I want to know about use case testing,if you could please provide video demo on that it would be very helpful for me.

[@QA1]

Pinky Many thanks for your comment. I have noted that you would like to learn use case testing.

[@pinky948]

Software and Testing Training Yes sir, I want to learn. I am prepareing for ISTQB exam so it will be helpful for me if you can give demo n use case testing.

[@QA1]

Pinky I have uploaded a new video on use case testing. Please find it at kzbin.info/www/bejne/fmqYg4trr6t_maM

[@DiscounedTravels]

Thanks for the tutorial which i find very useful. Just one thing you need to mention is the 0-switch and 1 - switch covers. can you please elaborate on these as I find them confusing. thanks

[@QA1]

H Mardi Thank you for your comment. 0 and 1 are the two possible states of the example lighting system. 0 means that the entire system is in the Off state (the switch is in the off state which causes the entire system, including the lighting and the circuit to be in the off state). 1 means that the entire system is in the On state i.e. the switch, the lamp and the circuit (with electricity flowing) is in the on state. The user of this system can only provide the input as the flick of the switch. The system changes state based on the user input and the current system state. Hope this clarifies it.

[@vinothp5921]

Hi I am new for Testing, i saw your Graph Based Testing, that video is very good to understand. Can you explain State Transition Testing for real time example, still i have doubt in your explanation. Advance appreciate for your positive replay.

[@QA1]

Vinoth P We can think of a software-based system as one with a finite number of states. For example, a text editor can be in exactly one of these states at a time - 1) Initial state; no text 2) Text entered; file not saved 3) Text entered; file saved etc. We can analyze the system requirements and determine the possible states and valid transitions between states. In state transition testing, we test that each valid transition is possible and works correctly. Also, each invalid transition is not allowed by the system. Does this clarify it? You can let me know if you have a specific question.

[@DiscounedTravels]

Thanks for the reply. Sorry I am still confused about the definition of 0-switch and 1-switch. According to sources, You can design tests to test every transition shown in the model. If every (valid) transition is tested, this is known as “0-switch” coverage. You could also test a series of transitions through more than one state. If you covered all of the pairs of two valid transitions, you would have “1-switch” coverage, covering the sets of 3 transitions would give “2-switch” coverage, etc" Based on the above, could you please elaborate on your example. I find your example very helpful but need to understand the 0 switch and 1 switch clearly as it is confusing especially difference between every valid transition and pairs of 2 valid transitions. Would appreciate if this is explained in a further example. thanks again

[@QA1]

H Mardi Well, I don't know about 0-switch and 1-switch. In my example, there is a lighting example with exactly one binary switch. At any time, this switch can be in the Off state or the On state. In state transition testing, we test if each valid transition works and if yes, it works correctly. There are two valid transitions in this example - Off to On (changes the state of the system to On i.e. the light is On) and On to Off (changes the state of the system to Off i.e. the light is On).

[@QA1]

H Mardi Just curious. When we have already tested each valid transition, why should we cover each couple or each triple of valid transitions? IMO, it is important to test each possible path in the state transition diagram. I have shown how to do this in my Car example. Thank you for your questions.

[@shibiyajoseph3203]

great and clear ...Thank you sir.....

[@QA1]

Shibiya - welcome to this channel.

[@suganyabasker4703]

Thanks

[@QA1]

@baskker b - Welcome to Software and Testing Training!

[@acs2377]

Hello, the minimum of test cases that can be written is defined by visiting each transition at least one, right? The reason I am asking is because i think we can create diffent test cases depending on the valid transitions selected.

[@QA1]

Actually, my approach is to first identify all the possible system states. Then identify all the possible valid transitions. We need to test each valid transition. This means we visit each "connected" state pair in our state transition diagram. Yes, you can create different test cases depending on which valid transition you test. The test cases in this video are based on workflows of a user and somewhat complex. Instead, we can have simple test cases that test that each valid transition is possible. And if possible, it changes the system state correctly. E.g. in this video of a valid transition is Stopped - Accelerating transition. Also, we need to test each invalid transition to test that it is not possible at all. E.g. in this video of an invalid transition is Stopped - Constant Speed transition. Many thanks for your question.

[@AbsolutelyNOW]

Very nice work :)Keep it up. :)

[@vijibharath1797]

Hello sir this is viji, ur explanations are amazing, can u plz explain cause effect graph

[@QA1]

Hi Viji, please see my video, Cause and Effect Analysis at kzbin.info/www/bejne/ppbdiqGaqL5qiq8

[@rufimn]

Hi, Could you give few real time examples of scenarios in an AUT/SUT where State Transition Technique can be used?? 2/ As in the previous black box techniques we used decision table technique first and then the EP/BVA for same input fields when needed.Can there be any scenarios in an AUT where we can use all 3 techniques for the same fields when needed??

[@QA1]

Per my knowledge, State Transition test design technique may be used for an entire system. But, since systems are typically complex, they have to be abstracted to a high level before this technique can be applied. A more common application of this technique is to test units of code like classes. 2) is a good question. State transition testing may be used first because it has less detail, if there is a manageable number of distinct states, then Decision Table testing and lastly, EP and BVA because that is the most detailed. Or the reverse order, if you want to test with most detail to least detail.

[@rufimn]

Great, Thankyou! Is there a connection between state transition and Usecase testing? For e.g in usecase testing when we give the example of interaction between an actor/customer and the bank, the state of the system also keeps on changing depending on the Pin number entered? I am understanding use-case testing according as per your video. Thanks,

[@QA1]

Thank you for your support. You may want to select your test design technique depending on how the requirements are documented. If there are use cases, it would be simpler to perform use case testing. For anyone reading this comment, the Use Case Testing tutorial is available at kzbin.info/www/bejne/fmqYg4trr6t_maM There is a difference in the format. In a use case, the focus is on the workflows. If you want to apply State Transition testing on the Cash withdrawal use case example, you have the additional step to write the state transition chart of the ATM system first.

[@rufimn]

You are welcome. You are always very helpful which encourages me to watch your videos ONLY among all other videos for the same topic on youtube :) 1/ If we are testing the interaction between the user and the system, why do we need to create testcases to test states and the transitions between states?? Is this the requirement given by customer to test both(Workflows and states/transitions)??? 2/I assume, the interaction between the customer and the system MUST be tested by creating Usecases ONLY, there is no other technique in BB to test this?? 3/There can be multiple Usecases in the TestDesign Specification document depending on the requirments , where each Usecase contain multiple testcases for normal and alternative workflows??? Thanks,

[@QA1]

Awesome, thanks again. My responses are: 1) No, no, let us not mix it up. If we have to test the interactions between the system and the user actor, we can simply write test cases from the normal workflow and exceptional workflow(s) of the use case. 2) Use case testing is one technique to test the system and user interactions. But, there are others like specification based, error guessing and exploratory testing. 3) Yes, but the Use Case steps have to be split into Test Case Steps and Expected Results.

[@TheFfgo]

perfect

[@seonyeollee1098]

Thank you so much. May I ask you a question? I want to generate a test suite that satisfies 0-switch or 1-switch coverage criteria with the fewest transitions . How can I do this? Thank you again.

[@QA1]

Please see if you get any help from the explanation at the link, rbcs-us.com/site/assets/files/1165/black-ast-state-diagrams-newsletter-2.pdf

[@technicalchannel967]

Thanks sr very much

[@QA1]

Many thanks for the like.

[@sweethad753]

Performing Integration testing using Visio diagram so here we say state transition technique involved?

[@QA1]

Yes, you can use your Visio diagram to represent the different states of a system and the transitions between those states. You can use your diagram to derive test cases that test the valid and invalid transitions. Or, as I explained in this tutorial, you may create a state table. It is easier to derive the test cases from the state table. There are many different tools that can be used to create state transition diagrams, such as Visio, ArgoUML, and State Tool. Thank you for your question. I hope this information is helpful 🙏

[@acs2377]

Can you please also explain the 0 switch and 1 switch coverage, thanks a lot.

[@QA1]

In the light switch example, we saw that the system can either be in the Off state or the On state. The system continues to be in its present state until a user input is given. There are only two valid state transitions in this system: 1 - Off state to On state 2 - On state to Off state In state transition testing, we test if each valid transition is possible or not. If the valid transition is possible, then it changes the system state correctly or not. Is this what you were looking? Please let me know.

[@TheNeotraceable]

Good work ,hello from Belgium

[@QA1]

TheNeotraceable Thank you and Best regards, Inder.

[@pandillapallisasikala5546]

Super ga chaparuu sir.big data kuda chapadee sir

[@QA1]

Thank you. Big Data tutorials at kzbin.info/aero/PLc3SzDYhhiGWebfydYhtzoVo5sZPaJuPh

[@pandillapallisasikala5546]

Thqs sir

[@vamsi8669]

In the Car analogy I think there should be another state call "decelerate" because the car cannot jump from constant speed to stop state without decelerating.Etc Etc...

[@QA1]

Bee Honey True. In my state transition diagram, I have labeled this state as Braking. Actually, Decelerating is a better label because it implies all states which lead to a reduction in speed e.g. braking, going up a slope, going against front wind etc.

[@adaseth]

" Braking doesn't make sense in a stopped car" - well I wouldn't like to stand behind you on a slope waiting for the light to turn green ;)

[@QA1]

This simple state transition diagram has distinct Stopped and Braking states. In order to make it more realistic (based on your comment), we will need to divide Stopped state into two distinct states, Stopped-Braking and Stopped-No braking. Perhaps another distinction is acceleration due to slope (e.g. downhill driving) OR pressing the gas pedal. Or braking due to slope (e.g. driving up an incline) or pressing the brake pedal. It is getting a bit complex so I will stop for now but thank you.

[@shahmeeriqbal9464]

does a state transition diagram count as a state transition testing method?

[@QA1]

No, a state transition diagram/ chart describes the system in terms of its valid (possible) states. We need to design the tests to check if every valid transition is possible. We can do this by traversing the state transition diagram. Thank you for your question.

[@JHANSIBALMURI]

👏👌

[@QA1]

@JHANSIBALMURI - Thank you 🙏

[@DiscounedTravels]

That s why I got confused. I mean your tutorial is clear but I want to understand the concept of 0 and 1 switch as well which this article mentions but its not clearly explained, istqbexamcertification.com/what-is-state-transition-testing-in-software-testing/s Perhaps you can explain it better

[@QA1]

H Mardi I saw switch coverage explained in detail at www.rbcs-us.com/images/documents/black-ast-state-diagrams-newsletter-2.pdf

[@hirashahid5028]

can you pls send me the slides? plssss

[@chand101989]

the example given is very bad, because in the example he is using car, while we are talking about software testing, i guess the example should be given from any real life testing scenario, like application state transistion from loging page to home page.

[@QA1]

The example given by you is good. But my example need not be considered to be a real car drive, rather the software representation of a car (as in a game). In fact, state transition diagram is much used in game testing.