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.

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

Upgrade testing across the lib #76

Closed
CPerezz opened this issue Aug 1, 2023 · 5 comments
Closed

Upgrade testing across the lib #76

CPerezz opened this issue Aug 1, 2023 · 5 comments
Assignees
Labels
T-test Type: test improvements

Comments

@CPerezz
Copy link
Member

CPerezz commented Aug 1, 2023

Would be nice to create macros that generate big testing suites for all the different field and curve implementations we have in the lib.

@CPerezz CPerezz added the T-test Type: test improvements label Aug 1, 2023
@CPerezz
Copy link
Member Author

CPerezz commented Sep 20, 2023

Could you assign me this issue ?

Feel free to reach for any need of help!

@nullity00 nullity00 removed their assignment Nov 3, 2023
@davidnevadoc davidnevadoc self-assigned this Nov 27, 2023
@duguorong009
Copy link
Contributor

duguorong009 commented Jan 11, 2024

@davidnevadoc
I'd like to pick up the issue, if it is not completed & you are busy with other stuff.
It would be grateful if you indicate what should be done to close the issue.

@CPerezz
Copy link
Member Author

CPerezz commented Jan 11, 2024

@davidnevadoc I'd like to pick up the issue, if it is not completed & you are busy with other stuff. It would be grateful if you indicate what should be done to close the issue.

I love this initiative! We indeed need serious improvements in our testing. And would be nice to land them prior to new releases.

@duguorong009
Copy link
Contributor

@davidnevadoc
We've merged 2 PRs for this issue - curve testing macros & field testing macros.
When can I start making the similar macros for pairing engine?

@davidnevadoc
Copy link
Contributor

@duguorong009 I'm currently taking care of the Bn curves refactor here #135

I think with these 2 PRs we can mark this issue as completed. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-test Type: test improvements
Projects
None yet
Development

No branches or pull requests

4 participants