Lines of code count not available
but maybe I want to have component left. You can run original script if want everything clean? I have some idea though
The script should not leave components because this can provide some issues on developer machine.
And we can't access stopped containers for some logs e.g.
but we need to remove them before next execution
because before all tests, we create a database dump which will probably contain data from the previous execution. It would be easier to simple stop containers after test.
But it doesn't work for requisition tooo
We do this only in the requisition tests.
Yeah, exactly. But why is it happening? I thought we clean db and load demo data before every scenario?
If you run twice tests for reference data, the second time some tests failed because "resource XYZ exists"
I'm wondering if it's possible to run tests multiple times on the same containers
we should probably stop containers after test complete
nice script. Could you update the README to show how to use it?
Got a suggestion or an issue?
Discuss it on Atlassian Answers or
visit Atlassian Support for other options.