-
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.
-
test-cases: add support for encrypted corpus
-
This is kind of a hack, hope this can be removed once other branch is merged (see code comment)
-
To avoid triggering antivirus engines, we can encrypt files with a default password and decrypt them before testing.
-
The OutputCapture was a slightly hacky way to get output from scripts without using subprocess. However, keeping it working started requiring reloads since module's logs are global variables which were re-initialized which caused trouble). That required reload of all submodules, so more hacks are needed to keep the initial hack "alive". Therefore I am glad it is not needed any more and can be removed.
-
Looking for reason for ResourceWarning abount unclosed BufferedReader, but this was not the cause...
-
With this change we replace the relative import. Also use with-statement to open test file, so file is always closed after reading (python3 unittest issued a warning).
-
Want to use the OutputCapture in another unit test. There will probably be more such test helpers over time that need to be imported from different unit tests.