Source Twilio: enable high
test strictness level in SAT
#19182
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
A
test_strictness_level
field was introduced to Source Acceptance Tests (SAT).Twilio is a generally_available connector, we want it to have a
high
test strictness level.This will help:
How
acceptance-test-config.yml
file to the latest configuration format. (See instructions here)high
test strictness level inacceptance-test-config.yml
. (See instructions here)If tests are failing please fix the failing test by changing the
acceptance-test-config.yml
file or usebypass_reason
fields to explain why a specific test can't be run.Please open a new PR if the new enabled tests help discover a new bug.
Once this bug fix is merged please rebase this branch and run
/test
again.You can find more details about the rules enforced by
high
test strictness level here.Review process
Please ask the
connector-operations
teams for review.