You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, developers must manually modify test code to reference a particular Spotter and expectations. Sofar should expose mock resources via testing API token(s) with known responses. The benefits would be:
Can run tests without modifying test code and referencing bespoke resources =>
Can repeat test results between devs
Enables automated CI/CD
Can increase specificity of integration test expectations. Currently the expectations are fairly generic, asserting a field exists, or a response does not err. With fixed and known data responses, we could enforce schema expectations, performance guardrails, regression protection against backend changes, etc.
The text was updated successfully, but these errors were encountered:
Currently, developers must manually modify test code to reference a particular Spotter and expectations. Sofar should expose mock resources via testing API token(s) with known responses. The benefits would be:
The text was updated successfully, but these errors were encountered: