-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/devel' into t-ramz-dev-container
- Loading branch information
Showing
56 changed files
with
4,662 additions
and
879 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
|
||
# You can override the included template(s) by including variable overrides | ||
# SAST customization: https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings | ||
# Secret Detection customization: https://docs.gitlab.com/ee/user/application_security/secret_detection/pipeline/#customization | ||
# Dependency Scanning customization: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#customizing-the-dependency-scanning-settings | ||
# Note that environment variables can be set in several places | ||
# See https://docs.gitlab.com/ee/ci/variables/#cicd-variable-precedence | ||
semgrep-sast: | ||
tags: | ||
- docker-exec | ||
variables: | ||
SECURE_LOG_LEVEL: "debug" | ||
rules: | ||
- if: $CI_PIPELINE_SOURCE == "push" | ||
|
||
secret_detection: | ||
stage: test | ||
tags: | ||
- docker-exec | ||
rules: | ||
- if: $CI_PIPELINE_SOURCE == "push" | ||
|
||
gemnasium-dependency_scanning: | ||
stage: test | ||
tags: | ||
- docker-exec | ||
rules: | ||
- if: $CI_PIPELINE_SOURCE == "push" | ||
|
||
include: | ||
- template: Security/Secret-Detection.gitlab-ci.yml | ||
- template: Security/SAST.gitlab-ci.yml | ||
- template: Security/Dependency-Scanning.gitlab-ci.yml |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# WARNING - Adding Tests | ||
|
||
Note The granularity of CMake is dependent on how they are defined in the CMakeLists.txt file. The tests are specified in | ||
CMake by passing a string that is matched against the chai test cases in the | ||
"it()" sections of the chai unit tests. Any test cases that match the pattern will run when that test is triggered. | ||
|
||
i.e. | ||
|
||
CMakeLists.txt line | ||
|
||
``` | ||
add_test(NAME foxx_record COMMAND "${CMAKE_CURRENT_SOURCE_DIR}/tests/test_foxx.sh" -t "unit_record") | ||
``` | ||
|
||
This will pass "unit_record" as the pattern to be matched to the test_foxx.sh | ||
script. In turn, the test_foxx.sh script will call foxx test with | ||
"unit_record". Tests are not matched based on the name of the test file they | ||
are matched based on the test cases. | ||
|
||
i.e. | ||
|
||
Below is part of a test case that would be matched against the "unit_record" pattern. | ||
|
||
``` | ||
describe('Record Class', () => { | ||
it('unit_record: isPathConsistent should return false paths are inconsistent in new and old alloc.', () => { | ||
: | ||
: | ||
}); | ||
it('unit_record: isPathConsistent a different test case.', () => { | ||
: | ||
: | ||
}); | ||
}); | ||
``` | ||
|
||
Notice that 'unit_record' is explicitly mentioned in the test cases. In the above exerpt, both tests will run. If ctest were to be explicitly called we could run all unit_record tests with the following. | ||
|
||
``` | ||
ctest -R foxx_record | ||
``` |
Oops, something went wrong.