-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unit tests for src/copybf.f, src/copymg.f, src/copysb.f, src/cpbfdx.f, src/cpdxmm.f, src/cpymem.f, src/cpyupd.f #33
Comments
Codes with apparently zero testing include:
So if these codes are important, they need to be tested. If they are not, they need to be removed. ;-) Getting at least a few tests for each subprogram should be a top priority unless there are urgent bugfixes or new releases that need to get out to users... These tests should be written in the style of intest1.F90:
|
With #331 we now have coverage for the following subprograms from the above list:
|
With the latest updates to #331 we now also have coverage for:
|
@jbathegit here's a question about copymg. If I run this code:
I get this error:
OK, the documentation had the answer! Now I have:
And it finds a message. ;-) |
I am taking a pass though these functions to see if bort testing can be improved. Here's the current testing levels for these functions:
These numbers will improve slightly when #415 is merged. |
Here's the current testing levels for these functions:
So some improvement, but still more testiing needed. |
Here's the current testing levels for these functions:
Seems like there are some error conditions in cpymem() and cpdxmm() that could be tested. However, overall, what a great improvement. |
Following the merging of some recent PRs, cpdxmm is now at 91% and cpymem is now at 97%. So I think we can close this one now. |
Nice! |
src/copybf.f, src/copymg.f, src/copysb.f, src/cpbfdx.f, src/cpdxmm.f, src/cpymem.f, src/cpyupd.f are all untested
The text was updated successfully, but these errors were encountered: