This PR adds smoke tests for some common scenarios.
The goal of the smoke tests is to increase confidence that the Docker image that is produced works as
intended.
The repo contains other tests, which are great, but what this PR adds is that it runs an integration
test using the following setup:
Build the Docker image
Run the Docker image with the tests directory mapped into the container
Run the Docker image's normal entrypoint (bin/run.sh) on each of the test cases defined in the
tests directory
Verify that the output of those test runs matches the expected output (which is stored inside the
tests directories
If successful, we then know that:
The Docker image can be built successfully
The bin/run.sh entrypoint inside the Docker image is setup correctly
The test runner generates the correct output
There were some PHP smoke tests too, but this new approach is more comprehensive I feek.
This PR adds smoke tests for some common scenarios.
The goal of the smoke tests is to increase confidence that the Docker image that is produced works as intended. The repo contains other tests, which are great, but what this PR adds is that it runs an integration test using the following setup:
tests
directory mapped into the containerbin/run.sh
) on each of the test cases defined in thetests
directorytests
directoriesIf successful, we then know that:
bin/run.sh
entrypoint inside the Docker image is setup correctlyThere were some PHP smoke tests too, but this new approach is more comprehensive I feek.