-
Notifications
You must be signed in to change notification settings - Fork 9
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
More detailed test cases #161
Labels
enhancement
New feature or request
infrastructure
Project infrastructure: dev tools, packaging, etc.
question
Further information is requested
testing
Work is related to testing
Comments
Saransh-cpp
added a commit
that referenced
this issue
Sep 23, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 24, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 25, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 25, 2024
This was referenced Sep 25, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 25, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 26, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 26, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 26, 2024
Saransh-cpp
added a commit
that referenced
this issue
Sep 27, 2024
paddyroddy
added
enhancement
New feature or request
infrastructure
Project infrastructure: dev tools, packaging, etc.
labels
Oct 7, 2024
Saransh-cpp
added a commit
that referenced
this issue
Oct 15, 2024
Saransh-cpp
added a commit
that referenced
this issue
Oct 16, 2024
The coverage went down when branch coverage was turned on. This PR brings it back to 100% for these two files. Refs: #161 Co-authored-by: Patrick J. Roddy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
infrastructure
Project infrastructure: dev tools, packaging, etc.
question
Further information is requested
testing
Work is related to testing
I find the test cases on the GitHub action quite sparse on details when they pass. I would like to see what has passed, and have some logging showing what has run, so I'm confident the full file has run correctly.
An easy improvement would be to call pytest with -v (verbose - shows individual test cases within the file) and -s (show print statements in the test cases) flags, for example.
Perhaps there is a prettier way of doing this, but I think this, with some simple logging (using print or otherwise) added to the test cases, would be a good first step
The text was updated successfully, but these errors were encountered: