| ... | @@ -8,6 +8,8 @@ The actions are described in https://github.com/nortikin/sverchok/blob/vstable10 |
... | @@ -8,6 +8,8 @@ The actions are described in https://github.com/nortikin/sverchok/blob/vstable10 |
|
|
- Python and libraries
|
|
- Python and libraries
|
|
|
3. running tests found in `./run_tests.sh` in the Sverchok main directory.
|
|
3. running tests found in `./run_tests.sh` in the Sverchok main directory.
|
|
|
4. two things can happen:
|
|
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 these tests run smoothly generally this means that the test suite has been able to cover all parts of sverchok where we have tests.
|
|
|
|
- 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.
|
|
- ❌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. |
|
|
|
\ No newline at end of file |
