Skip to content

Conversation

@alexgromero
Copy link
Contributor

@alexgromero alexgromero commented Dec 2, 2025

Issue #, if available:

Description of changes:
This PR adds comprehensive integration tests for Amazon Transcribe Streaming client covering the following streaming patterns:

  • Non-streaming operation using get_medical_scribe_stream (requires setup)
  • Bidirectional streaming operation using start_stream_transcription

Non-streaming Test Setup:
The get_medical_scribe_stream test requires AWS resources (IAM role + S3 bucket). A setup script is included at tests/setup_resources.py that creates these resources. The test fails if the required environment variables (HEALTHSCRIBE_ROLE_ARN and HEALTHSCRIBE_S3_BUCKET) are not set.

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

@alexgromero alexgromero requested a review from a team as a code owner December 2, 2025 20:45
Copy link
Contributor

@nateprewitt nateprewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few minor comments but otherwise looks like we're all set. Thanks @alexgromero!

alexgromero and others added 2 commits December 2, 2025 16:18
…directional_streaming.py

Co-authored-by: Nate Prewitt <nate.prewitt@gmail.com>
Copy link
Contributor

@nateprewitt nateprewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last minor comment, otherwise we're ready to merge I think.

Comment on lines 48 to 49
assert role_arn, "HEALTHSCRIBE_ROLE_ARN environment variable not set"
assert s3_bucket, "HEALTHSCRIBE_S3_BUCKET environment variable not set"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can definitely do this approach, what I was asking about earlier was using pytest.fail instead of pytest.skip though. The explicit test failure let's us surface the configuration issue in one message rather than having to run the script multiple times for the asserts.

The asserts are there to enforce something about the test rather than setup ideally.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh got it! Updated in latest revision.

Copy link
Contributor

@nateprewitt nateprewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@alexgromero alexgromero merged commit 1ca29c6 into awslabs:develop Dec 3, 2025
@alexgromero alexgromero deleted the transcribe-streaming-integration-tests branch December 3, 2025 16:56
nateprewitt added a commit that referenced this pull request Jan 2, 2026
* Add integration tests for Bedrock Runtime (#37)

* Add integration tests for Transcribe Streaming (#38)

* Update integration tests to use the latest Amazon Nova 2 models (#39)

* Update to latest bedrock-runtime model

* Release: aws-sdk-bedrock-runtime-0.3.0

* Release: AWS SDK Transcribe Streaming 0.3.0

* Release: AWS SDK Sagemaker Runtime HTTP2 0.3.0

* Release: aws-sdk-python 0.3.0

---------

Co-authored-by: Alessandra Romero <24320222+alexgromero@users.noreply.github.com>
Co-authored-by: jonathan343 <43360731+jonathan343@users.noreply.github.com>
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.

2 participants