Certified Tester Model-Based Tester Free Sample Questions

One of the primary benefits of MBT is reduced maintenance effort. When system behavior (logic) changes, only the model needs to be updated. The test cases (abstract and concrete) can then be automatically regenerated, ensuring the test suite stays synchronized with requirements.

This is True. The adaptation layer works bi-directionally. It concretizes abstract test inputs to drive the SUT, and it abstracts concrete SUT outputs back to the model level to compare against the oracle (expected abstract results).

All-Transitions Coverage ensures that every transition in the state model is traversed at least once by the generated test cases. This is a stronger criterion than All-States, which only requires visiting every state.

Formalizing requirements into a model (like a state transition diagram) is the core activity of the MBT Modeling phase. The other options relate to implementation (adaptation layer) or execution.

BPMN is specifically designed for workflow modeling, emphasizing the sequence of activities, gateways (decisions), and flow of business processes. Statecharts focus on the object/system lifecycle states, which is less suitable for a process flow.

An abstract test case is a path through the model (sequence of inputs/expected outputs) expressed in the model's terminology. It lacks the low-level details (like specific button IDs or API endpoints) needed for execution, making it implementation-independent.

A major pitfall is expecting immediate ROI. Building the initial models and adaptation layer requires significant upfront effort and new skills, often leading to disappointment if expectations aren't managed.

Trying to 'boil the ocean' by modeling everything at once usually leads to complexity overload and failure. Successful deployments typically start with a small, manageable pilot.

N-Switch coverage requires traversing sequences of N+1 transitions. Even a 1-Switch coverage (pairs of transitions) is stronger than All-Transitions (which is essentially 0-Switch). It detects defects related to history/sequence, not just single steps.

The Test Adapter is the specific component responsible for translating abstract commands (e.g., 'Login') into concrete SUT actions (e.g., 'POST /api/login with user=X').

According to the diagram, the flow is Draft --(submit)--> Review --(approve)--> Approved --(publish)--> Published. This matches the sequence 'submit -> approve -> publish'.