I am a little bit confused with the "state transition modeling" technique used for testing.
On a high-level, we have 3 major states when a user logs into the application under test:
- logged out
- logging in
- logged in / dashboard
But, during logging in, our application under test makes multiple asynchronous requests to different API endpoints. I'd like to explore if there are any potential problems related to order of the received responses, or if some of the responses were never sent, network timeouts etc.
Should I break the "logging in" state into multiple smaller states? How deep and inter-connected, in general, should the state transition tables/diagrams be? Are there any best-practices?