white-box-red-testing

Yes, you can generate adversarial tests during a code review by specifying a scope like commits, files, or coverage thresholds. The workflow outputs red tests with structured rationale without modifying your source code.

You generate adversarial tests by manually invoking the red-testing workflow on your chosen scope, such as specific files or commits. The tool then outputs red tests with structured rationale for each bug found.

Yes, this red-testing workflow requires a test framework like pytest or an equivalent. It uses these frameworks to output red tests that expose bugs in your targeted code areas.

No, this bug detection process is non-destructive and does not modify your source code. It only analyzes the targeted areas and outputs red tests with clear rationale for each finding.

The best way to stress-test code coverage thresholds is to set coverage as your scope in an adversarial red-testing workflow. This generates red tests designed to break the code and identify gaps in your coverage.