There can be a problem if such file already exists and is open for writing (that is, busy).
It can probably happen with multithreaded test runs.
Set environment variables
Same as with file, but directly set up env variables.
There's a risk of overwriting the value that was already set.
However, if it was set before running the tests, the reporter should have read and used it.
Test reporters create a Qase test run before reporting the tests. Subsequent CI steps might need the information about the run for many reasons:
Implementation
There can be several options to return the values:
Write variables to a file
qase.sh
There can be a problem if such file already exists and is open for writing (that is, busy). It can probably happen with multithreaded test runs.
Set environment variables
Same as with file, but directly set up env variables. There's a risk of overwriting the value that was already set. However, if it was set before running the tests, the reporter should have read and used it.
Write values to stdout in a well-parseable format