-
Kirill Smelkov authored
Currently Nexedi takes mostly a copy-paste approach when it comes to organizing bin/runTestSuite and an instance to run this inside testnode: kirr@deco:~/src/wendelin/slapos/slapos-master$ git ls-files |grep runTestSuite software/build-rina/runTestSuite.in software/buildout-testing/runTestSuite.in software/cython-test/runTestSuite.in software/erp5testnode/testsuite/deploy-test/runTestSuite.py software/jstestnode/runTestSuite.in software/neoppod/runTestSuite.in software/neoppod/stress-testing/runTestSuite.in software/unstable/pyodide/runTestSuite.in and adding new tests to be run this way will only increase the entropy. Let's stop this, at least for new tests, and use a uniform approach without copying: 1) I've created nxdtest tool[1] which allows a project to specify in declarative way how to test itself: given such declaration nxdtest takes on itself the responsibility to communicate with testnode master, to drive test commands spawning etc, ...
0dd3e119