Test Contract
An executable agreement inspired by the contract-testing approach in software engineering. It specifies five elements: customer scenario, simulated account state, expected behavior, the bot under test, and evaluation dimensions. It decouples "what to test" from "who implements it," enabling different bot implementations to be compared under a unified standard.
Timeline (last 90 days)
Autopilot uses a shared test contract, and each flow and test contract specifies five elements: the customer scenario, the simulated account state, the expected behavior, the bot under test, and the aspects being evaluated.
The test contract borrows the idea of contract testing from software engineering, in which the consumer and provider agree on an executable contract regarding interface behavior, and any change by either party must be verified against the same contract.
All Facts (2)
Autopilot uses a shared test contract, and each flow and test contract specifies five elements: the customer scenario, the simulated account state, the expected behavior, the bot under test, and the aspects being evaluated.
50%UnverifiedThe test contract borrows the idea of contract testing from software engineering, in which the consumer and provider agree on an executable contract regarding interface behavior, and any change by either party must be verified against the same contract.
50%