Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Always use property based testing where possible #76

Open
Tracked by #49
Fi3 opened this issue Nov 17, 2021 · 1 comment
Open
Tracked by #49

Always use property based testing where possible #76

Fi3 opened this issue Nov 17, 2021 · 1 comment
Assignees
@rrybarczyk
Labels
test Test related
Milestone
Error(s) refactor...

Comments

@Fi3
Copy link
Collaborator

Fi3 commented Nov 17, 2021

No description provided.

@Fi3 Fi3 mentioned this issue Nov 17, 2021
Open
8 tasks
@Fi3
Copy link
Collaborator Author

Fi3 commented Mar 31, 2022

That means that each lib crate of the workspace should have a test framework that resemble the one that we have on sv2-ffi.

@rrybarczyk rrybarczyk changed the title use the sv2-ffi prop tests as an example to create a test framework for each crate in the project Always use property based testing where possible Sep 16, 2022
@rrybarczyk rrybarczyk added the test Test related label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rrybarczyk rrybarczyk

Labels
test Test related
Projects
No open projects
Sv2 Project Plan 2022
Status: In Progress 🏗️
Milestone
Error(s) refactored, good code covera...
Development

No branches or pull requests
2 participants
@Fi3 @rrybarczyk