Difference between revisions of "Acceptance Tests"
Jump to navigation
Jump to search
Access restrictions were established for this page. If you see this message, you have no access to this page.
| Line 7: | Line 7: | ||
:* '''Running “life-like scenarios”''' | :* '''Running “life-like scenarios”''' | ||
:* '''In a “production-like test environment”.''' | :* '''In a “production-like test environment”.''' | ||
They are the first step in the [[Acceptance Stage]] of a [[Deployment Pipeline]], and an important one. | |||
[[Acceptance Tests]] represent one of the key 'gates' in making progress with our [[Release Candidate]]s. | |||
This is the first time that we evaluate our software in the form that it will be deployed into [[Production]]. | |||
Revision as of 13:21, 5 August 2021
In Brian Marick's Test Quadrant model, Acceptance Tests are "business facing" tests that "support the team".
Acceptance Tests are written:
- From the perspective of an “external user of the system”
- Running “life-like scenarios”
- In a “production-like test environment”.
They are the first step in the Acceptance Stage of a Deployment Pipeline, and an important one.
Acceptance Tests represent one of the key 'gates' in making progress with our Release Candidates.
This is the first time that we evaluate our software in the form that it will be deployed into Production.