You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A nice feature of Testers2 is that it bases the name of the work directory for a test from the scalaTest test name. This can lead to potential collisions if two different tests share the same tests name.
Proposed fix, incorporate class name of test into the test directory
Example
classXextendsFreeSpecwithChiselScalatestTester {
"basic compile should work" in {}
}
classYextendsFreeSpecwithChiselScalatestTester {
"basic compile should work" in {}
}
The working directory for both these tests will be the same, i.e. "test_run_dir/basic_compile_should_work".
It might not matter but it can create weird errors if the the two tests are similar and have different backends.
The text was updated successfully, but these errors were encountered:
A nice feature of Testers2 is that it bases the name of the work directory for a test from the scalaTest test name. This can lead to potential collisions if two different tests share the same tests name.
Proposed fix, incorporate class name of test into the test directory
Example
The working directory for both these tests will be the same, i.e. "test_run_dir/basic_compile_should_work".
It might not matter but it can create weird errors if the the two tests are similar and have different backends.
The text was updated successfully, but these errors were encountered: