|
|
|
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
|
|
|
|
|
|
|
|
1. getting a harddrive in the cloud
|
|
|
|
2. (re)storing an image of a drive that has
|
|
|
|
- Blender
|
|
|
|
- Sverchok `any branch`
|
|
|
|
- Python and libraries
|
|
|
|
3. running tests found in `./run_tests.sh` in the Sverchok main directory.
|
|
|
|
4. two things can happen:
|
|
|
|
- ✔️if these tests run smoothly the test suite has been able to cover all parts of sverchok where we have tests
|
|
|
|
- ❌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. |
|
|
|
\ No newline at end of file |
