-
Notifications
You must be signed in to change notification settings - Fork 13
Add integration tests for Transcribe Streaming #38
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
Add integration tests for Transcribe Streaming #38
Conversation
nateprewitt
left a comment
There was a problem hiding this 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!
clients/aws-sdk-transcribe-streaming/tests/integration/test_bidirectional_streaming.py
Outdated
Show resolved
Hide resolved
clients/aws-sdk-transcribe-streaming/tests/integration/test_bidirectional_streaming.py
Show resolved
Hide resolved
clients/aws-sdk-transcribe-streaming/tests/integration/test_non_streaming.py
Show resolved
Hide resolved
clients/aws-sdk-transcribe-streaming/tests/integration/test_non_streaming.py
Outdated
Show resolved
Hide resolved
clients/aws-sdk-transcribe-streaming/tests/integration/test_non_streaming.py
Show resolved
Hide resolved
…directional_streaming.py Co-authored-by: Nate Prewitt <nate.prewitt@gmail.com>
nateprewitt
left a comment
There was a problem hiding this 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.
| assert role_arn, "HEALTHSCRIBE_ROLE_ARN environment variable not set" | ||
| assert s3_bucket, "HEALTHSCRIBE_S3_BUCKET environment variable not set" |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
nateprewitt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
![]()
* 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>
Issue #, if available:
Description of changes:
This PR adds comprehensive integration tests for Amazon Transcribe Streaming client covering the following streaming patterns:
get_medical_scribe_stream(requires setup)start_stream_transcriptionNon-streaming Test Setup:
The
get_medical_scribe_streamtest requires AWS resources (IAM role + S3 bucket). A setup script is included attests/setup_resources.pythat creates these resources. The test fails if the required environment variables (HEALTHSCRIBE_ROLE_ARNandHEALTHSCRIBE_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.