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
After running the unit tests there are two files that are left behind: did_recovery and did_recovered. I think that they are created in the directory from where the unit test is invoked. Probably creating a temporary directory and deleting it after the specific unit test is a good idea.
If simplemonitor gets packaged in some other distribution/operating system: it might make packaging easier
I haven't verified this but potentially it could cause a false positive: if a test creates the file, the code gets broken but the file in some environment is still there: perhaps a test passes but the code is broken
The text was updated successfully, but these errors were encountered:
After running the unit tests there are two files that are left behind:
did_recovery
anddid_recovered
. I think that they are created in the directory from where the unit test is invoked. Probably creating a temporary directory and deleting it after the specific unit test is a good idea.Why am I reporting it?
The text was updated successfully, but these errors were encountered: