An error occurred fetching the project authors.
- 02 Dec, 2020 1 commit
-
-
Xavier Thompson authored
-
- 27 Nov, 2020 1 commit
-
-
Jérome Perrin authored
Change to run all tests with python -m unittest, which will allow us to remove workaround for the $PYTHONPATH set by setup.py test. For this we use `[python-interpreter]` which uses pygolang.main to behave like a "normal" python interpreter with eggs available, but without the usual problems of interpreters generated by zc.recipe.eggs - it supports all command line flags and have current directory in sys.path. Tests now have an explicit name, that we set to the software name as before, and the special test dynamically checking all profiles json schemas (part of slapos.cookbook egg, at the root of slapos repository),is named json-schemas. It is also changed to run as default tests in python2 and python3, not only in extras for python2.
-
- 05 Aug, 2020 1 commit
-
-
Jérome Perrin authored
Using an script to set the environment is easier to use, but the main reason is that if we want to be able to use shared part from outer slapos (like when using in theia or slaprunner), the working directory for test must be contained in the instance directory of the outer slapos, so that when we run slapos node prune in the outer slapos this command can see that shared parts are used.
-
- 06 Mar, 2020 1 commit
-
-
Jérome Perrin authored
and other probably useful information.
-
- 20 Dec, 2018 1 commit
-
-
Łukasz Nowak authored
Since some software releases have unit tests, it is good idea to run the tests for each commit on slapos branch. This SR follow slapos-testing SR in a way how tests are grouped and run. Fixed erp5.util is used to expose good test suite names.
-