You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The file Dockerfile_test can be used to generate a docker container that runs the tests and outputs a results.xml. I have no idea of how we can get the file from the container. docker cp ... did not work for me locally.
A dockerfile is not supposed to execute containers it is for building images that, in this case, are supposed to contain dependencies needed for later execution of an application in the container. Your Dockerfile runs the test in what is the build phase of the image which is not the correct way of doing this as it should just install python-opencv in that case.
You would later use the generated image to start up a container that will then run the tests. A container can then have the repo mounted as volume (e.g. using -v argument to the docker run command) to use it as the workspace for executing the tests.
Resulting artifacts stored in this workspace will be available in the mounted workspace and thus also outside of the container.
For Jenkins it's not really necessary to have an additional script also executing tests in the container as in our case it could take care of that inside a given container but it's not bad to have something for local testing or reference.
Der current development branch produces xunit style results.
Run the following commands
in PROJECT_HOME to get the results in testreports.
The lines above create a new virtual environment under
.venv
, active it, install the dependencies and run the unittests.The text was updated successfully, but these errors were encountered: