Where tests should run
Up until now, we have executed our test manually on our PC. That is fine, and it is mandatory during the development phase. However, this is not enough because our installation could be edited, or we could have some uncommitted files.
To solve this issue, it is possible to add a Continuous Integration (CI) pipeline that runs remotely to manage our repository. The CI pipeline’s primary duties are as follows:
- Running the test suite to check the code in the remote Git repository
- Building a code base to create artifacts if necessary
- Releasing the artifacts by triggering a Continuous Delivery (CD) pipeline to deploy the software
The CI workflow will notify us about its status, and if it is in a red state, the application’s tests are failing with the last commit. Running the test remotely will prevent false-positive issues due to our local environment setup.
We will build a simple CI workflow by adopting GitHub Actions. This...
