Non-exhaustive testing #1599
Merged
Non-exhaustive testing #1599
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
|
Nice! Is there going to be a PointFree episode dedicated to this or will I have to actually read documentation? :) |
mbrandonw
reviewed
Oct 31, 2022
mbrandonw
reviewed
Oct 31, 2022
Sources/ComposableArchitecture/Documentation.docc/Articles/Testing.md
Outdated
Show resolved
Hide resolved
No episode is planned for this change, but we may discuss it in future episodes. 😁 |
Co-authored-by: Brandon Williams <[email protected]>
…ting.md Co-authored-by: Brandon Williams <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces the ability to configure a test store's level of exhaustivity. We have always promoted TCA's exhaustive testing as a great feature, and it's helped us and others catch many bugs quickly over the years.
This thoroughness isn't without its pitfalls, though, especially when testing the integration of several reducers. We've seen this firsthand in larger applications, like isowords, and other TCA users have battled with it, as well.
This led @krzysztofzablocki to propose a "non-exhaustive" test store, which would allow you to dial in your assertions to focus on just what you care about. After working together, we're bringing this functionality into the Composable Architecture in a configurable way.