Make use of pFUnit test fixtures #238
Merged
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
jwallwork23
added
autograd
jwallwork23
force-pushed
the
236_unit-test-fixtures
branch
2 times, most recently
from
397daeb to
d696e4d
Compare
jwallwork23
force-pushed
the
236_unit-test-fixtures
branch
from
d696e4d to
449846d
Compare
|
I recommend viewing the changes in this file offline with |
jatkinson1000
approved these changes
Jan 23, 2025
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.
Closes #236.
To follow #231 and #237 (rebased on top of those branches).
Sets up the pFUnit fixture machinery for the
test_tensor_constructorsunit tests.To do this, I needed to convert the unit tests to use modules. A benefit of doing so is that common imports and parameters could be moved to the module level. (As such, many of the lines changed are just indentations of the unit tests.)