-
Notifications
You must be signed in to change notification settings - Fork 24
fix(tests): resolve issue with 'exception' status raising failure of FAST container tests #606
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
Conversation
…FAST container tests
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.
Pull Request Overview
This PR fixes an issue in the FAST container tests by updating the expected outcome mapping to include an "exception" status.
- Added a mapping for the "exception" status (same as "failed") to the ExpectedOutcome.
- Updated the error message to indicate the new valid status, "exception".
Comments suppressed due to low confidence (2)
airbyte_cdk/test/models/outcome.py:35
- [nitpick] The inline comment notes that 'exception' is the same as 'failed'. Consider adding a brief explanation for this mapping duplication to clarify its intent for future maintainers.
"exception": ExpectedOutcome.EXPECT_EXCEPTION, # same as 'failed'
airbyte_cdk/test/models/outcome.py:40
- Verify that the updated error message aligns with any test assertions or external documentation. Adjust tests if they expect a different wording than the newly provided message.
) from ex
📝 WalkthroughWalkthroughThe updates add the Changes
Sequence Diagram(s)sequenceDiagram
participant Developer
participant GitHub Actions
participant Connector Test Matrix
Developer->>GitHub Actions: Push changes
GitHub Actions->>Connector Test Matrix: Run tests (including source-google-ads)
Connector Test Matrix-->>GitHub Actions: Report test results
GitHub Actions-->>Developer: CI status (with source-google-ads included)
sequenceDiagram
participant TestCase
participant ExpectedOutcome
TestCase->>ExpectedOutcome: from_status_str("exception")
ExpectedOutcome-->>TestCase: Return EXPECT_EXCEPTION
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🔇 Additional comments (3)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Resolves
Invalid status 'exception'. Expected 'succeed' or 'failed'.
:in
Thanks to @tolik0 for raising.
Summary by CodeRabbit
Chores
Bug Fixes
Important
Auto-merge enabled.
This PR is set to merge automatically when all requirements are met.