Skip to content

Add proxy tests for the AppSync service #120

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.

Sign up for GitHub

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

Open
whummer wants to merge 3 commits into
base: main
Choose a base branch
from
+406 −3
Open

Add proxy tests for the AppSync service #120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bd3bbb2
add proxy tests for the AppSync service
whummer Jan 24, 2026
50dc8f2
fix flaky kinesis readonly test with retry on put_record
whummer Jan 24, 2026
4ae81b8
update AGENTS.md
whummer Jan 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions aws-proxy/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ You are an AI agent tasked with adding additional functionality or test coverage
* You can call different `make` targets (e.g., `make test`) in this repo (no need to prompt for confirmation)
* For each new file created or existing file modified, add a header comment to the file, something like `# Note/disclosure: This file has been (partially or fully) generated by an AI agent.`
* The proxy tests are executed against real AWS and may incur some costs, so rather than executing the entire test suite or entire modules, focus the testing on individual test functions within a module only.
* Before claiming success, always double-check against real AWS (via `aws` CLI commands) that everything has been cleaned up and there are no leftover resources from the proxy tests.
* Never add any `print(..)` statements to the code - use a logger to report any status to the user, if required.
* To format/lint the codebase you can run `make format` and `make lint`.

Expand Down
Loading