[tests] Refactor the testing files for BigInt and BigUInt
#106
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
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 refactors the testing files for
BigIntandBigUInttests/bigint/test_bigint_arithmetics.mojo) to use a data-driven approach by loading test cases from TOML files, significantly reducing code duplication and improving maintainability.load_test_casesfunction (src/decimojo/tests. Mojo) with a newunaryparameter to differentiate between single and multi-operand tests.BigUIntwhich first generate very big (>20000 digits) integers, floor divide them using both DeciMojo and Python's int type, and compare them.