When a PR is merged, it should - as a minimum - not break the most essential use cases for APInf.
Connect the automated end-to-end tests for Gate 1 to Travis CI build. If necessary, create seed data, e.g. an admin user. Refer to issue #2671 for more information on the seed data.
Goal:
Each time a Travis build is made for a PR, the Gate 1 tests are also run.
When testing this for the first time, check whether the tests are passing. If the tests do not pass because of outdated tests, create an issue for updating the tests with a list of required changes.
Note: Consider whether Gate 2 should also be run for each PR.
ilarimikkonen
commented
6 years ago
Description:
When a PR is merged, it should - as a minimum - not break the most essential use cases for APInf. Connect the automated end-to-end tests for Gate 1 to Travis CI build. If necessary, create seed data, e.g. an admin user. Refer to issue #2671 for more information on the seed data.
Goal:
Note: Consider whether Gate 2 should also be run for each PR.