test: add e2e test for evaluations lifecycle#628
Merged
Conversation
6eed8a7 to
61b6f9f
Compare
61b6f9f to
94f181f
Compare
94f181f to
2c8784e
Compare
ec089b6 to
0eae153
Compare
0eae153 to
8599456
Compare
8599456 to
256bc9f
Compare
256bc9f to
9419081
Compare
9419081 to
81529cb
Compare
tejaskash
approved these changes
Mar 24, 2026
Contributor
tejaskash
left a comment
There was a problem hiding this comment.
Looks good. Clean refactoring of e2e helpers and solid evals lifecycle test coverage.
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
The evaluations feature (custom evaluators, online eval configs, on-demand evals, pause/resume) is missing e2e test coverage. This PR adds a standalone e2e suite that tests the full lifecycle against real AWS infrastructure.
Also refactor e2e test setup to be build consumable utility functions rather than a single mono-function.
Known limitation:
logs evalsnot includedOnline eval log processing is async and the CloudWatch log group (
/aws/bedrock-agentcore/evaluations/results/{configId}) was not populated within 8+ minutes of polling across multiple test runs. This makeslogs evalsassertions unreliable for e2e testing.Related Issue
Closes #
Documentation PR
N/A — test-only change.
Type of Change
Testing
How have you tested the change?
npm run test:unitandnpm run test:integnpm run typechecknpm run lintsrc/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsVerified against dev account (us-east-1). All 6 tests pass in ~4 minutes:
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.