• We want to run unit tests against a built Docker image and not by installing the environment inside Gitlab CI runner
• We don't want to push the docker image to a registry and pull it back in a test job to run unit tests - it's slower.

But it contradicts the separation of concerns principle - now our build job will also run unit tests.

The question for the community: is this okay to sacrifice this principle in this case or there are better alternatives?

• We want to run unit tests against a built Docker image and not by installing the environment inside Gitlab CI runner
• We don't want to push the docker image to a registry and pull it back in a test job to run unit tests - it's slower.

But it contradicts the separation of concerns principle - now our build job will also run unit tests.

The question for the community: is it okay to sacrifice this principle in this case or there are better alternatives?