Logical Operations Testing #37
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
AzeezIsh
force-pushed
the
logical_testing
branch
from
fed07da to
7e46cca
Compare
syurkevi
approved these changes
Apr 12, 2024
added 5 commits
April 12, 2024 17:16
Added several logical tests
Tested for shapes and datatypes
syurkevi
force-pushed
the
logical_testing
branch
from
5bd4c99 to
76970d5
Compare
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 introduces a suite of unit tests for logical_operations.py located within the within the mathematical functions directory. The primary functions in this file are based around classic bit-based operations like and, not, or, etc.
General Functionality: Tests confirm that the library accurately handles functionality across various array shapes and dimensions, ensuring these operations perform correctly from scalars up to four-dimensional arrays. This encompasses verifying the maintenance of result dimensions in accordance with input shapes.
Data Type and Edge Case Handling: The library's robustness is tested against a comprehensive set of data types including integers, floating-points, and complex numbers (where applicable), affirming operation compatibility and precision.