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
{{ message }}
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.
When IO tests fail, the files tests/test.pos_1.pdb and tests/test.pos_1.xyz can be left in the working tree. The easiest way to do it is probably using with_setup and making sure the files are gone:
This might be more robust than trying to make sure that the test function itself is always able to clean up after itself. Another option would be to use a test class (instead of test functions), which can have its own setup and cleanup. Other suggestions are welcome, of course. Whatever the solution, it should be reused for all tests that write files.
The text was updated successfully, but these errors were encountered:
When IO tests fail, the files
tests/test.pos_1.pdb
andtests/test.pos_1.xyz
can be left in the working tree. The easiest way to do it is probably usingwith_setup
and making sure the files are gone:https://nose.readthedocs.org/en/latest/writing_tests.html#test-functions
This might be more robust than trying to make sure that the test function itself is always able to clean up after itself. Another option would be to use a test class (instead of test functions), which can have its own setup and cleanup. Other suggestions are welcome, of course. Whatever the solution, it should be reused for all tests that write files.
The text was updated successfully, but these errors were encountered: