Skip to content

test(memory): add stream delivery integ tests, and TESTING.md#317

Merged
jariy17 merged 1 commit into
aws:mainfrom
Hweinstock:feature/memory-integ-tests
Mar 11, 2026
Merged

test(memory): add stream delivery integ tests, and TESTING.md#317
jariy17 merged 1 commit into
aws:mainfrom
Hweinstock:feature/memory-integ-tests

Conversation

@Hweinstock

@Hweinstock Hweinstock commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Issue #, if available: N/A

Description of changes:

Problem

Memory integration tests have no documentation for running locally, and there is no test coverage for the streamDeliveryResources feature.

Solution

  • Added TESTING.md at repo root with instructions for running all integration test suites locally, including prerequisites, environment variables, and conventions for new tests.
  • Added basic integration test class that verifies that a given delivery config is reflected in the data returned by the service.
  • Add necessary permissions to existing memory role
  • Add a kinesis stream arn secret to actions.

Testing

  • Ran the tests against my personal account.
  • Ran the tests against the CI account with new role and kinesis stream.

Note: it takes ~2-3 minutes due to memory provisioning delay.

Future Work

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 0ed3195 to 335f694 Compare March 10, 2026 20:24
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 335f694 to 98d31d8 Compare March 10, 2026 20:42
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 98d31d8 to 51e780b Compare March 10, 2026 20:47
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 51e780b to 7a00b08 Compare March 10, 2026 21:50
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 7a00b08 to 2ba6267 Compare March 10, 2026 22:44
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch 2 times, most recently from 2492661 to 18c0d0a Compare March 10, 2026 23:21
@codecov-commenter

codecov-commenter commented Mar 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@98100d7). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #317   +/-   ##
=======================================
  Coverage        ?   90.87%           
=======================================
  Files           ?       42           
  Lines           ?     4033           
  Branches        ?      618           
=======================================
  Hits            ?     3665           
  Misses          ?      202           
  Partials        ?      166           
Flag Coverage Δ
unittests 90.87% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch 6 times, most recently from 0f91e7f to 668d524 Compare March 11, 2026 12:17
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch 3 times, most recently from 3f43b1a to a4de01f Compare March 11, 2026 12:27
@Hweinstock Hweinstock marked this pull request as ready for review March 11, 2026 12:31
@Hweinstock Hweinstock requested a review from a team March 11, 2026 12:31
Hweinstock added a commit to Hweinstock/bedrock-agentcore-sdk-python that referenced this pull request Mar 11, 2026
Add update_memory to MemoryClient so developers no longer need to drop
down to MemoryControlPlaneClient to update memory properties like
description, event expiry, execution role, or stream delivery config.

- Builds params dict with only provided fields (same pattern as create_memory)
- Calls gmcp_client.update_memory and normalizes response
- Removes update_memory from _ALLOWED_GMCP_METHODS (explicit method replaces forwarding)
- Unit tests: param passthrough, normalization, omitted params, minimal params, ClientError
- Integration test: builds on PR aws#317 TestStreamDeliveryResources class with
  test_stream_delivery_update (FULL_CONTENT -> METADATA_ONLY with wait/poll)
Hweinstock added a commit to Hweinstock/bedrock-agentcore-sdk-python that referenced this pull request Mar 11, 2026
Add a focused method to update stream delivery configuration on a memory
without requiring callers to drop down to MemoryControlPlaneClient.

- Calls gmcp_client.update_memory with only memoryId, clientToken, and
  streamDeliveryResources — no other memory properties are modified
- Normalizes response via _normalize_memory_response
- Does not shadow the existing update_memory passthrough in _ALLOWED_GMCP_METHODS
- Unit tests: config passthrough, response normalization, ClientError propagation
- Integration test: builds on PR aws#317 TestStreamDeliveryResources with
  test_stream_delivery_update (FULL_CONTENT -> METADATA_ONLY with wait/poll)
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch 3 times, most recently from b3df0db to 4218416 Compare March 11, 2026 18:05
@Hweinstock

Hweinstock commented Mar 11, 2026

Copy link
Copy Markdown
Contributor Author

As discussed in person, going to adjust this PR by proposing a set of testing guidelines for future integ tests to help maintain consistency.

@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch 2 times, most recently from 682b8e1 to 23db03e Compare March 11, 2026 18:12
@Hweinstock Hweinstock force-pushed the feature/memory-integ-tests branch from 23db03e to 138d561 Compare March 11, 2026 18:24
@jariy17 jariy17 merged commit 32aa019 into aws:main Mar 11, 2026
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants