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
Please check how to capture error messages when running tox. I forgot to configure the JS engines in my environment (add binaries under js_engines) and could not see any indication of what was happening besides a FAIL in test cases.
The text was updated successfully, but these errors were encountered:
I wrote a script that checks if radamsa and the engines are installed on environment (before run our tests).
Keep updating this issue if you (or me) encounter new problems on tox.
But what I meant was to see meaningful error messages if something bad if a test fails. I think what we should do is to separate two kinds of executions: regression_tests and fuzzing. In regression_test it is fine if multiple tests fail. it indicates a problem in our infrastructure and if that happens it we should not proceed with fuzzing, which should depend on that target (using make terminology). In the fuzzing target, no test should fail. A failing execution indicates that something is broken in our infrastructure--we should stop immediately.
damorim
changed the title
tox does not generate error message
tox does not generate error messages
Apr 23, 2018
Please check how to capture error messages when running tox. I forgot to configure the JS engines in my environment (add binaries under js_engines) and could not see any indication of what was happening besides a FAIL in test cases.
The text was updated successfully, but these errors were encountered: