-
Notifications
You must be signed in to change notification settings - Fork 233
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
helper/resource/testing_new: update import state testing #550
helper/resource/testing_new: update import state testing #550
Conversation
6fd9dfb
to
eaf066a
Compare
eaf066a
to
9ad7a3f
Compare
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.
Outsider approval -- not sure about any testing to prevent future regressions. 😄
This would also close #528 in its current form. |
Co-authored-by: Brian Flad <[email protected]>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
1 similar comment
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Closes #532
testStepNewImportState
can now return the error (if any) of the underlying method that imports the resource, thus allowing for error handling w/inrunNewTest
whenstep.ImportState
is set totrue
. Special error handling is needed here to account for provider acceptance tests that check for expected errors duringImportState
test steps as illustrated in #532.Output of previously failing acceptance test: