Not much, but as discussed in #100 I've added class tearDown method, which is executed after all tests have passed (or not 😅). Thanks to this little change we create .marathonTests folder only once (and it's lazy), plus, we remove it at the end of running our test suite, so there are no artifacts in user's file system.
Looks like there's a problem with running class func tearDown() in --parallel mode... Strange, cause it does what it should (removes folder), but looks like it can't handle parallelism... 😓
Not much, but as discussed in #100 I've added
class tearDown
method, which is executed after all tests have passed (or not 😅). Thanks to this little change we create.marathonTests
folder only once (and it'slazy
), plus, we remove it at the end of running our test suite, so there are no artifacts in user's file system.