-
Decrypting test samples "on the fly" using a generator causes trouble when removing the temp file, PyPy/Windows thinks the file is still being used.
-
(1) Cannot open a temp file for writing from 2 python processes simultaneously (2) Need proper environment setup for Popen (thanks to metatoaster's reply on stackoverflow https://stackoverflow.com/a/72845540/4405656) (3) Need different os-separator, so replace hard-coded '/' with os.path.join or os.sep (4) Minor cleanup of imports & whitespace in test_issue_*.py There are still 2 tests that should be adapted to Windows, but those are lower-prio in my eyes. Also, unittest run on my windows VM creates many resource warnings due to non-closed file descriptors. Should address that some (future) day.
-
Some samples triggered antivirus engines, issues #215 and #217 ended with the agreement to encapsulate problematic samples in encrypted zip containers and decrypt them on-the-fly. Initial support for this was added but that did not cover 5 tests. Create on-the-fly decryption for these tests as well and re-enable them.
-
…porary workaround for #398), corresponding test files are now zipped with password 'infected-test' (for #215)
-
json is messed up in pypy with warnings
-
Prevent unwanted FileNotFoundError caused by wrong test code shadow actual msodde output
-
When adapting the test a while ago, Samir forgot that this one test tested with multiple args. That was unnecessary, anyway, so removed them.
-
Some msodde tests call the main() function from the module which tries to enable logging, causing lots of problems when running multiple tests due to the singleton dependency of the logging modules. Since what they want to test is whether msodde is finding links, we can use the process_file() function directly instead and check its output.
-
They actually found a few \ in strings I had overlooked
-
Will add excel test code and samples later, no need to have separate folders for different file types.