|
|
|
We use Github actions to trigger a set of tests of the sverchok code base after a commit to the any Sverchok branch.
|
|
|
|
The actions are described in https://github.com/nortikin/sverchok/blob/vstable10/.github/workflows/test-sverchok.yml and involve
|
|
|
|
|
|
|
|
## test-sverchok.yml
|
|
|
|
|
|
|
|
1. getting a harddrive in the cloud
|
|
|
|
2. (re)storing an image of a drive that has
|
|
|
|
- Blender
|
| ... | ... | @@ -12,4 +14,20 @@ The actions are described in https://github.com/nortikin/sverchok/blob/vstable10 |
|
|
|
- this does not mean that there are no bugs.
|
|
|
|
- in some cases the test suite itself ends early due to a bug in code that isn't tested, therefore it is a good idea to frequently look at the output of the tests to see if indeed all tests have completed. A green tick is not a guarantee for a bugfree sverchok.
|
|
|
|
- ❌if the tests fail, one ore more tests didn't complete as expected and we'll look into it.
|
|
|
|
5. if this was the first run, the image of the drive is stored (cached, section '2') and can be reused after the next commit to Master. |
|
|
\ Нет новой строки в конце файла |
|
|
|
5. if this was the first run, the image of the drive is stored (cached, section '2') and can be reused after the next commit to Master.
|
|
|
|
|
|
|
|
## run_tests.sh
|
|
|
|
|
|
|
|
(or the equivalent windows command `run_tests_win.bat`)
|
|
|
|
|
|
|
|
roughly looks like this
|
|
|
|
```bash
|
|
|
|
$BLENDER -b --addons sverchok --python utils/testing.py
|
|
|
|
```
|
|
|
|
- start blender in background mode
|
|
|
|
- enable sverchok
|
|
|
|
- execute sverchok/utils/testing.py
|
|
|
|
|
|
|
|
## testing.py
|
|
|
|
|
|
|
|
This is where we define all tests of geometry, list matching, import, export, loading .blends . |
|
|
\ Нет новой строки в конце файла |
