This repository has been archived by the owner on May 27, 2023. It is now read-only.
Improved exception handling on fixture loader #147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please separate your pull request into two different functionalities:
|
|
@IvanChepurnyi: Can you please outline what you mean by separating the pull request? Like doing two pull requests? I'm asking because I'm interested about the exception handling and information giving about the fixture that tells with which testcase it was interacting. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Wrapped the fixture load in an exception handler which adds the name of the test case to the exception message. This helps track down which test case is having issues with fixtures in a large test suite.