Acceptance tests for requirements verification.

In software development, an acceptance test is the verification of whether software features work as intended by the user, who does specific checks (also known as validations) to «accept» or «reject» them. Acceptance tests consist of acceptance criteria. Each of these criteria has only two possible outcomes: «true / valid» or «false / invalid». Acceptance tests should be repeated over the entire life cycle of a software product.

praxisIcon

PRACTICE

It is also a good practice to implement such tests as automated regression tests

It is also a good practice to implement such tests as automated regression tests. Regression tests repeat test cases to ensure that previously tested and then modified parts of the software do not cause new bugs («regressions»).

The topic «Test-Engineering»

We specialize in the «test engineering» of complex software components (SAP, enterprise applications) and their interfaces (microservices, APIs) and offer know how in the following areas:

FORMULATION OF ACCEPTANCE TESTS

Drafting of acceptance tests as narrative specifications using behaviour-driven languages («BDD» or «Specification-Driven Development – SDD»).

REVIEW OF ACCEPTANCE TESTS

Continuous verification of acceptance tests by integration in agile (e.g. JIRA) and CI/CD or DevOps tools

INTEGRATION

Integration into development cycles by means of regression tests driven by models, templates and data.