Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Automated Test Suite #133

Merged
merged 4 commits into from
Jan 10, 2025
Merged

Define Automated Test Suite #133

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ba26705
Define Automated Test Suite
david-a-wheeler Jan 10, 2025
c53f55b
Update baseline.yaml
david-a-wheeler Jan 10, 2025
689ca2a
Update baseline.yaml
david-a-wheeler Jan 10, 2025
db60171
Update baseline.yaml
SecurityCRob Jan 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions baseline.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -861,6 +861,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.
david-a-wheeler marked this conversation as resolved.
Show resolved Hide resolved
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
Loading