Skip to content

Commit

Permalink
Define Automated Test Suite (#133)
Browse files Browse the repository at this point in the history
* Define Automated Test Suite

Signed-off-by: David A. Wheeler <[email protected]>

* Update baseline.yaml

Signed-off-by: David A. Wheeler <[email protected]>

* Update baseline.yaml

Signed-off-by: David A. Wheeler <[email protected]>

* Update baseline.yaml

Co-authored-by: Ben Cotton <[email protected]>
Signed-off-by: CRob <[email protected]>

---------

Signed-off-by: David A. Wheeler <[email protected]>
Signed-off-by: CRob <[email protected]>
Co-authored-by: CRob <[email protected]>
Co-authored-by: Ben Cotton <[email protected]>
  • Loading branch information
3 people authored Jan 10, 2025
1 parent ceed906 commit 41ca66f
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions baseline.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -987,6 +987,14 @@ lexicon:
Code provided by an external source that is
executed by a system without validation or
restriction.
- term: Automated Test Suite
definition: |
A collection of pre-written test cases that, when invoked,
execute the software to verify that actual results are expected results
without requiring manual intervention.
An automated test suite must return an overall "pass" or "fail" result,
and is often implemented using a test framework.
Common ways to invoke automated tests include `make check`, `make test`, `npm test`, and `cargo test` manually or as part of a Continuous Integration workflow.
- term: Build and Release Pipeline
definition: |
A series of automated processes that compile
Expand Down

0 comments on commit 41ca66f

Please sign in to comment.