add property-based tests for audio #15
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I cannot check why the deployment failed... EVen though I have an account, Vercel prevents me from landing in the Deployment failure page.. 404 (maybe due to permissions) |
|
@sharabash @osamasayed could you please help on this ? |
|
@ahmedriad1 any issue on this ? anything I could do to unblock it ? |
|
No response, so I'm closing this abandoned PR. |
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 integrates
fast-checkproperty-based testing into the existing test suite to ensure that the spy calls on thefetcherfunction match the expected API calls. The tests now cover multiple scenarios and edge cases, dynamically generating inputs to validate the robustness of the API interaction.Key changes include:
By employing property-based testing, we aim to catch more bugs by checking the correctness of the code against a broader set of possible inputs. This should lead to a more reliable and maintainable codebase.