Abstract: Embodiments allow a mock-enabled software module to access a store of mock output data. Sets of mock output values (“SMOVs”), stored within the mock output store, are mapped to one or more key input values. When input sent to a mock-enabled software module includes one or more key input values that map to a given SMOV, the SMOV is included in a mock response from a target module of the given SMOV. When a set of input values, sent to a mock-enabled software module, does not include key input values that map to a SMOV, the mock-enabled module produces output without triggering any mock response. The mock output store may contain one or more replacement templates that are used to replace one or more mock output values, in a mock response, with one or more corresponding input values from the set of input values received by the triggering module.