IDE & Navigation
Properties & Tools
The state node is used to represent a state in your model. Note a state may contain children states, which is called a super state. If you have a large model, super state is useful to organize states in groups making a large model much easier to work with and test.
The state node should contain at least one transition leading to another state and should have at least one transition pointing to it from another state.
Drag and drop a state to another state moves the state into another state. Drage and drop a state to an mCase does not move the state, instead it creates test step(s) in mCase that represents the state or transition copied previously.
New in release 2.1: when the state verification fails it usually causes the rest of the test to fail as AUT is not in the correct state. With new state url, you can reset the state and the rest of your testing can continue.
New in release 3.0: you may attach a submodel to a state. A submodel is another MBT model which can be included in different models. When a submodel is attached to a state, it is populated with all states/transitions from the submodel including mScripts, but they should not be changed from the model referencing it.