TEST Add Crescendo scenario resume coverage - #2343
Merged
Roman Lutz (romanlutz) merged 3 commits intoAug 7, 2026
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0d1f97bd-49a5-4a6d-b814-fecef1e2a8cb
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 67c023ca-8b50-48de-88f1-0e2cc3025996
varunj-msft
approved these changes
Aug 7, 2026
Roman Lutz (romanlutz)
deleted the
romanlutz-scenario-crescendo-resume-test
branch
August 7, 2026 20:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Crescendo scenario recovery needs end-to-end regression coverage to ensure retries and resumed runs do not leak stale state between objectives. This adds a test-only scenario using real PyRIT orchestration, attack, target, scorer, and SQLite memory components while mocking only the OpenAI SDK request boundary.
The two-objective schedule covers rate limiting, timeout persistence, malformed adversarial responses, refusal backtracking, partial failure, and successful resume. It also verifies conversation attribution, retry metadata, run-state transitions, unique persisted records, and scorer inputs.
Tests and Documentation
uv run --offline --no-sync pytest tests/unit/scenario/core/test_scenario_crescendo_resume.py -q(1 passed)uv run --offline --no-sync pytest tests/unit/scenario/core tests/unit/executor/attack/multi_turn/test_crescendo.py -q(508 passed before merging currentmain)uv run --offline --no-sync ruff format --check tests/unit/scenario/core/test_scenario_crescendo_resume.pyuv run --offline --no-sync ruff check tests/unit/scenario/core/test_scenario_crescendo_resume.pyuv run --offline --no-sync ty check tests/unit/scenario/core/test_scenario_crescendo_resume.pygit diff --checkOnline dependency resolution was blocked by a PyPI TLS handshake failure, so validation used the frozen dependency set restored from the local
uvcache. Documentation and JupyText are not applicable to this test-only change.