-
Notifications
You must be signed in to change notification settings - Fork 103
test(#3928): add behaviour scenarios for URL-sourced harness dispatch #5407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
5438572
test(#3928): add behaviour scenarios for URL-sourced harness dispatch
fullsend-ai-coder[bot] f45f2f5
fix(#3928): make harness-hosting repos ephemeral with per-lease naming
fullsend-ai-coder[bot] a51c1ff
fix(#3928): always re-vendor CLI binary in behaviour ensure
fullsend-ai-coder[bot] af7677a
test(#3928): add unit tests for URL dispatch coverage gaps
fullsend-ai-coder[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,128 @@ | ||
| Feature: URL-sourced harness dispatch | ||
|
|
||
| Background: | ||
| Given the enrolled test repository | ||
| And a harness-hosting repository "url-harness-host" | ||
|
|
||
| Scenario: URL-sourced harness with CEL trigger dispatches agent | ||
| Given a URL-sourced custom harness "url-ping" with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-url-ping | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-url-ping" | ||
| """ | ||
| And a dummy agent that would: | ||
| | description | op | args | | ||
| | Issue URL set | assert_env | GITHUB_ISSUE_URL | | ||
| | Prove URL execution | write_fixture| output/dispatch-url-ok.json, fixtures/dispatch/ok.json | | ||
| And an issue | ||
| When the issue is labeled "ready-for-url-ping" | ||
| Then the harness "url-ping" workflow completes successfully | ||
| And the agent will succeed to Prove URL execution | ||
|
|
||
| Scenario: Config mixes URL-sourced and local harnesses | ||
| Given a custom harness "local-ping" with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-local-ping | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-mixed-ping" | ||
| """ | ||
| And a URL-sourced custom harness "url-mixed" with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-url-mixed | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-url-mixed-ping" | ||
| """ | ||
| And a dummy agent that would: | ||
| | description | op | args | | ||
| | Prove local execution | write_fixture| output/dispatch-local-ok.json, fixtures/dispatch/ok.json | | ||
| And an issue | ||
| When the issue is labeled "ready-for-mixed-ping" | ||
| Then the harness "local-ping" workflow completes successfully | ||
|
ifireball marked this conversation as resolved.
|
||
| And the agent will succeed to Prove local execution | ||
|
|
||
| Scenario: URL source with bad integrity hash is skipped and dispatch continues | ||
| Given a custom harness "good-local" with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-good-local | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-integrity-test" | ||
| """ | ||
| And a URL-sourced custom harness "bad-hash" with bad integrity hash: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-bad-hash | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-integrity-test" | ||
| """ | ||
| And a dummy agent that would: | ||
| | description | op | args | | ||
| | Prove fallback execution | write_fixture| output/dispatch-fallback-ok.json, fixtures/dispatch/ok.json | | ||
| And an issue | ||
| When the issue is labeled "ready-for-integrity-test" | ||
| Then the harness "good-local" workflow completes successfully | ||
| And the agent will succeed to Prove fallback execution | ||
| And the harness "bad-hash" agent did not run | ||
|
|
||
| Scenario: URL source not in allowlist fails config validation | ||
| # Production ValidateAgentEntries hard-fails the entire config when any | ||
| # URL agent is outside allowed_remote_resources. No agents dispatch — | ||
| # including the valid local harness — because config validation fails | ||
| # before agent resolution begins. | ||
| Given a custom harness "good-allowed" with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-good-allowed | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-allowlist-test" | ||
| """ | ||
| And a URL-sourced custom harness "no-allow" not in allowlist with: | ||
| """ | ||
| agent: agents/triage.md | ||
| role: triage | ||
| slug: fullsend-ai-no-allow | ||
| model: opus | ||
| image: ghcr.io/fullsend-ai/fullsend-sandbox:latest | ||
| trigger: | | ||
| event.entity.kind == "work_item" | ||
| && event.transition.kind == "label_changed" | ||
| && event.transition.label.name == "ready-for-allowlist-test" | ||
| """ | ||
| And an issue | ||
| When the issue is labeled "ready-for-allowlist-test" | ||
| Then the harness "good-allowed" agent did not run | ||
| And the harness "no-allow" agent did not run | ||
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.