-
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
change 'Tests Run' and 'Passed' to reflect the number of testcases instead of the number of assertions #180
Milestone
Comments
"number of testcases" = the number of files, right? And "Total Test Count" is already capturing that. What marklogic-unit-test calls a
|
peetkes
added a commit
to peetkes/marklogic-unit-test
that referenced
this issue
Aug 11, 2023
…me of the tests
peetkes
added a commit
to peetkes/marklogic-unit-test
that referenced
this issue
Aug 12, 2023
…me of the tests
rjrudin
added a commit
that referenced
this issue
Sep 5, 2023
Also fixing a bug where setup/teardown modules were being counted in the number of tests. Also removed duplication of logic from default.xqy, which is now using the "is" functions in test-controller.xqy. Added a few of these functions for syntactic sugar as well, just to make the code easier to read in default.xqy. We unfortunately don't have any tests for the default.xqy module, so this is being tested manually via ml-gradle's unit-test-example project.
Addressed via #195 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the GUI the Suite overview gives
A suite can have multiple testcases and each testcase can have multiple assertions.
But as soon as a testcase has a single failed assertion, the whole testcase is flagged as failed regardless of the number of succeeded assertions up until the failure.
So the count of assertions is not that informative.
I would suggest changing the 'Tests Run' to the number of testcases that were executed and 'Passed' to the number of successful run testcases.
This can be changed in test-controller.xqy lines 183, 184 and 185
The text was updated successfully, but these errors were encountered: