When you run tests in parallel with scalatest, you can miss some allure-results files. It caused by different from java frameworks (testng, junit) test threads behaviours in scalatest. Allure-scalatest knows about this point, but it was a bug in stopTest behaviour: this method worked as in java-style and tried to get UUID of test case from internal allure thread holder class. In multithreading launches in scalatest threads sometimes have changed and we can't find UUID by thread in allure internal threadlocal storage. So in such cases we can't write a test result to file.
fixes #945
Context
When you run tests in parallel with scalatest, you can miss some allure-results files. It caused by different from java frameworks (testng, junit) test threads behaviours in scalatest. Allure-scalatest knows about this point, but it was a bug in stopTest behaviour: this method worked as in java-style and tried to get UUID of test case from internal allure thread holder class. In multithreading launches in scalatest threads sometimes have changed and we can't find UUID by thread in allure internal threadlocal storage. So in such cases we can't write a test result to file.
Checklist