Skip to content

Acceptance Tests
Compare
Choose a tag to compare
@tjazerzen tjazerzen released this 12 May 10:39
· 3 commits to main since this release
v0.1.7
c0ed9c3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

We’re excited to introduce a powerful new feature in the Plain language: Acceptance Tests.

Acceptance tests can be used to further refine the functional requirement and especially to incorporate constraints on the implementation.

Acceptance tests are specified with a keyword ***Acceptance Tests:*** as a subsection within ***Functional Requirements:*** section. Each acceptance test must be an item in a list.

Here's an example of a "Hello, World" application with one acceptance test.

***Functional Requirements:***

- Display "hello, world"

  ***Acceptance Tests:***
    
  - The App shouldn't show logging output in the console output (neither in stdout nor stderr).

Acceptance tests extend conformance tests. The acceptance tests are implemented according to the Test Requirements: specification (see next section).

If you have any questions or feedback, we’d love to hear from you.

Assets 2
Loading