written by Tatjana Statescu
Recently I shared with you how we use smoke testing as a pillar of our QA strategy.
We organize our automatic tests logically into test suites and run them as part of the pipelines, triggered by code push and merge hooks.
Often though, we would like to run a test suite on-demand, without having to bump code.
We can simply check out the test repository locally, and run tests from the local machine. However, that is both time-consuming and error-prone.
We thought it would be better if we could run test suites on-demand from Gitlab CI. We decided we would like to trigger tests from:
- the Gitlab user interface
- another CI pipeline
- a Slack channel
In this article, I describe how we set up those three, using our smoke tests as a prime example.
If you like this kind of QA automation content and are considering a new role, please check out our current jobs.