-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add coverage tests for PSP modules #435
Comments
I don't see coverage analysis in CI for PSP. Could that be added to show what's covered or not for the entire submodule? Looks like there's an issue from 2015 :) #18 |
Adds a coverage test implementation for all existing PSP modules. This should get 100% coverage on all lines and branches.
I believe we only run the coverage tests as part of the CI for the entire bundle. In theory we could make a script that just builds the PSP coverage tests and does so under the PSP CI. We should also make the results more visible. However that will have to be done as a follow-on as the stakeholders want the coverage tests ASAP. |
Adds a coverage test implementation for all existing PSP modules. This should get 100% coverage on all lines and branches.
Adds a coverage test implementation for all existing PSP modules. This should get 100% coverage on all lines and branches.
Implements handlers to mimic old stub behavior whenever possible
Fix #435, add coverage tests for PSP modules
The handler executes after the stub count increments, thus this needs to check for 1 to indicate the first call, not 0.
Fix #435, add coverage tests for PSP modules
Is your feature request related to a problem? Please describe.
The coverage testing on PSP modules is not complete. There is only a coverage test for 2 of the modules, but not the rest.
Describe the solution you'd like
Add coverage testing functions for all PSP modules
Describe alternatives you've considered
N/A
Additional context
Customer/Stakeholder requirement
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: