Split unit test code into separate filees #144
Merged
Conversation
This file contains hidden or 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
jkmassel
force-pushed
the
swift-package-unit-test
branch
from
2ff550e to
08ea213
Compare
jkmassel
approved these changes
Jun 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 says in the title. There is no new code in this RP.
I'm planing to add more unit tests to the Swift package. There will be some unit tests on REST endpoints, but it's likely they'll be "happy path" tests. Because we have great coverage in the Rust integration tests.
The unit tests in Swift package will be focus on platform specific things, like error handling. Or maybe even smoke tests where we make an actual REST API call to make sure it returns successful results on all supported platforms.