024a1ce260
add known issues to this file so that they will be exculded in CI results |
||
---|---|---|
.. | ||
CIConfigs | ||
TestCaseScript | ||
InitialConditionAll.yml | ||
KnownIssues | ||
README.md | ||
TestCaseAll.yml | ||
TestEnvAll.yml |
The test folder in SDK
File Structure
test --- CIConfigs --- sanity_test1.yml (Runner config files)
| |-- stress_test1.yml
|-- TestCaseAll.yml (TestCaseFiles)
|-- TestEnvAll.yml (TestCaseFiles)
|-- InitialConditionAll.yml (TestCaseFiles)
|-- TestCaseScript --- ... (Test case scripts)
- CIConfigs folder
- config for CI config files are put in this folder
- CI config files configs the cases and some other options for the CI job with same name
- Test case files
- TestCaseAll.yml (test cases)
- InitialConditionAll.yml (initial conditions)
- TestEnvAll.yml (test environments)
- how to modify test cases
- Test case scripts
- some cases are implemented by specified script. those scripts are put in this folder.
Modify test cases
- check if the "SDK" of the test case only contain the current SDK
- if Yes, then just modify the test case behavior
- if No:
- then remove current SDK name from "SDK" of the test case
- Add a new test case, and set "SDK" only support current SDK name
- use auto_test_script to load the modified case and verify the modification
- create a merge request and assign to HYL (or add comment @yinling for merging test). After review it will be merged to SDK and will be The cases will be synced to database in auto_test_script.
Run test case locally
- clone auto_test_script (ssh://git@gitlab.espressif.cn:27227/yinling/auto_test_script.git) from gitlab
- create test environment:
- search test case (search test case ID in components/test/TestCaseAll.yml, get the "test environment" value
- goto test environment list, find the link and goto the environment detail page
- create test environment according to figure and description
- config test environment. All parameters in table "Parameters require config before use" MUST be configured.
- run test cases with CIRunner.py