Running your test suite under es-python

[eyal-gabay]

Your tests already drive your code down the paths that matter. Run them under es-python and every flow they exercise is checked, with no new tests to write:

es-python -m pytest

What people usually find useful to know first:

• A new machine watches network input and file reads. A test suite often feeds data in other ways, so look at the stdin, env and db_rows sources in Taint sources and switch on the ones your tests use.
• Each run is its own group on the dashboard, so you can look at one run's events and nothing else. See Runs.
• In a pipeline, the CI driver can fail the build on what a run finds. See Run es-python in CI.

A longer write-up: Running your pytest suite under the EyalSec Python runtime.

If you have run a suite this way, what did the first run show you that you did not expect?