Tests creating unwanted artifacts #239

New issue

Closed

opened 2020-10-18 01:15:39 -07:00 by scionaltera · 1 comment

scionaltera commented

2020-10-18 01:15:39 -07:00

(Migrated from github.com)

I've started noticing that running the unit tests with ./gradlew clean build can create a force-close file unexpectedly that doesn't get cleaned up at the end of the tests.

Ideally I'd like to figure out a clean way to properly mock the ConditionService tests and any others that create files so they no longer need to create real files, but I'd settle for figuring out which test is failing to clean up after itself and fixing that.

I've started noticing that running the unit tests with `./gradlew clean build` can create a `force-close` file unexpectedly that doesn't get cleaned up at the end of the tests. Ideally I'd like to figure out a clean way to properly mock the `ConditionService` tests and any others that create files so they no longer need to create real files, but I'd settle for figuring out which test is failing to clean up after itself and fixing that.

scionaltera commented

2020-12-19 00:15:02 -08:00

(Migrated from github.com)

This seems to be due to pitest mutating the tests in ways that leave files on the disk. It doesn't happen when I only run JUnit.

Commenting is not possible because the repository is archived.