yuzu-emu/mbedtls
1
0
Fork 0
mirror of https://github.com/yuzu-emu/mbedtls.git synced 2024-11-26 10:55:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

Rename Python scripts to use '_' and not '-'

Browse Source 
You can't import a Python script whose name includes '-'.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
Gilles Peskine 2020-06-25 14:18:34 +02:00
parent 68a98516f6
commit fb4f933f8e
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/architecture/testing/test-framework.md
View File

@ -22,7 +22,7 @@ Each test case has a description which succinctly describes for a human audience
* Make the description descriptive. “foo: x=2, y=4” is more descriptive than “foo #2”. “foo: 0<x<y, both even” is even better if these inequalities and parities are why this particular test data was chosen. * Make the description descriptive. “foo: x=2, y=4” is more descriptive than “foo #2”. “foo: 0<x<y, both even” is even better if these inequalities and parities are why this particular test data was chosen.
* Avoid changing the description of an existing test case without a good reason. This breaks the tracking of failures across CI runs, since this tracking is based on the descriptions. * Avoid changing the description of an existing test case without a good reason. This breaks the tracking of failures across CI runs, since this tracking is based on the descriptions.
`tests/scripts/check-test-cases.py` enforces some rules and warns if some guidelines are violated. `tests/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
## TLS tests ## TLS tests
@ -32,7 +32,7 @@ Each test case has a description which succinctly describes for a human audience
Each test case in `ssl-opt.sh` has a description which succinctly describes for a human audience what the test does. The test description is the first parameter to `run_tests`. Each test case in `ssl-opt.sh` has a description which succinctly describes for a human audience what the test does. The test description is the first parameter to `run_tests`.
The same rules and guidelines apply as for [unit test descriptions](#unit-test-descriptions). In addition, the description must be written on the same line as `run_test`, in double quotes, for the sake of `check-test-cases.py`. The same rules and guidelines apply as for [unit test descriptions](#unit-test-descriptions). In addition, the description must be written on the same line as `run_test`, in double quotes, for the sake of `check_test_cases.py`.
## Running tests ## Running tests

4
tests/scripts/all.sh
View File

@ -680,7 +680,7 @@ component_check_doxy_blocks () {
component_check_files () { component_check_files () {
msg "Check: file sanity checks (permissions, encodings)" # < 1s msg "Check: file sanity checks (permissions, encodings)" # < 1s
record_status tests/scripts/check-files.py record_status tests/scripts/check_files.py
} }
component_check_changelog () { component_check_changelog () {
@ -707,7 +707,7 @@ component_check_test_cases () {
else else
opt='' opt=''
fi fi
record_status tests/scripts/check-test-cases.py $opt record_status tests/scripts/check_test_cases.py $opt
unset opt unset opt
} }

0
tests/scripts/check-files.py → tests/scripts/check_files.py
View File

0
tests/scripts/check-test-cases.py → tests/scripts/check_test_cases.py
View File