[Solved] In a banking app, the states are LoggedOut, LoggedIn, Locked. Transitions:LoggedOut -login-> LoggedInLoggedIn -logout-> LoggedOutLoggedIn -fail_attempt-> LockedLocked -reset-> LoggedOutIf a user... | Testing Fundamentals

Testing Fundamentals - Functional Testing Techniques

In a banking app, the states are LoggedOut, LoggedIn, Locked. Transitions:
LoggedOut -login-> LoggedIn
LoggedIn -logout-> LoggedOut
LoggedIn -fail_attempt-> Locked
Locked -reset-> LoggedOut
If a user fails login twice, then resets, then logs in successfully, what is the final state?

ALocked

BError

CLoggedOut

DLoggedIn

Step-by-Step Solution

Solution:

Step 1: Trace the events step-by-step
Start at LoggedOut. Two 'fail_attempt' events from LoggedOut do not cause transitions, so user remains LoggedOut. Then 'reset' from LoggedOut keeps user LoggedOut. Finally, 'login' moves LoggedOut to LoggedIn.
Step 2: Determine final state
After all events, the user is LoggedIn.
Final Answer:
LoggedIn -> Option D
Quick Check:
Event sequence ends in LoggedIn state [OK]

Quick Trick: Check if events cause transitions from current state [OK]

Common Mistakes:

Assuming fail_attempt from LoggedOut changes state
Ignoring reset effect
Confusing Locked and LoggedOut states

Master "Functional Testing Techniques" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Trace Try Challenge Automate Recall Frame

More Testing Fundamentals Quizzes

In a banking app, the states are LoggedOut, LoggedIn, Locked. Transitions:

Step 1: Trace the events step-by-step

Step 2: Determine final state

Final Answer:

Quick Check:

Want More Practice?