testomatio / docs

Documentation for Testomatio
https://docs.testomat.io/
2 stars 0 forks source link

Document auto-merge strategy for --update-ids #40

Open poliarush opened 10 months ago

poliarush commented 10 months ago

Hi, the question I have for you is around the lifecycle of testing with CI. Is the preferred method Create tests in IDE, Import from the local machine via CLI or browser. Tests ids are synched to code then committed. Tests execute in CI and results are received.

My real question is if a developer creates new test(s) in their IDE. Commits the test(s). CI imports tests. It seems the test will not have a test id. How does that impact what is received and displayed in testomat?

--

Hi, a very good question and I think that was the part we need to document better so thanks for your question, I will pick it up as the starting point to describe the flow.

I would recommend using CI job which imports tests with --update-ids option, which adds IDs to all tests on every commit to main branch.

To ensure that IDs are saved I would also have this job to auto-merge its changes. If you use GitHub Actions I can recommend this action to be included https://github.com/emiliopedrollo/auto-merge

So this makes the flow fully automated

poliarush commented 10 months ago

https://docs.testomat.io/usage/continuous-integration#assigning-ids