Releases: marklogic-community/marklogic-unit-test
1.4.0
This minor release addresses the following items:
- #14
assert-same-values
now works for JSON arrays (though the arrays must have simple values of the same type). - #77
TestManager
now has methods for selecting a subset of suites and tests to run. ml-gradle 4.6.0 will utilize this via itsmlUnitTest
task. - #87
test:get-test-data-path
was extracted and made public to allow for test developers to easily query for test data URIs. - #112
test:assert-true
now correctly fails for values ofnull
,undefined
, and an empty sequence. - #180 The labels in the test runner user interface were improved to be more accurate; "Total Test Count" is now "Test Cases" and "Tests Run" is "Assertions".
1.3.0
1.2.1
1.2.0
This minor release addresses multiple security vulnerabilities caused by the Spring framework.
- org.springframework:spring-context:5.3.9->5.3.18
- org.springframework:spring-test:5.3.9->5.3.18
- ml-javaclient-util:4.3.0->4.3.1
- marklogic-client-api:5.5.0->5.5.3
Also, bumped jackson-databind from 2.11.1 to 2.12.6.1 due to a security vulnerability detected by dependabot.
1.1.0
This minor release addresses several issues ; highlights:
- #129 Upgraded to Java Client 5.5.0, and all other dependencies were upgraded to the latest version
- #134 Now published to Maven Central
Due to #134, you no longer need to include "jcenter" as a repository in your Gradle or Maven files. jcenter has effectively been deprecated , and Maven Central should now be used for accessing marklogic-unit-test artifacts.
MarkLogic Unit Test Version 1.0.0
Implemented enhancements:
- assert-equal-json no longer reports the location of comparison differences #37
- Add documentation for developing and testing ml-unit-test locally #29
- Support Testing of the MarkLogic Data Hub Framework (DHF) #26
- Support testing of REST services #25
- Setup real JUnit tests for marklogic-unit-test-modules #11
Fixed bugs:
Closed issues:
- ML10 gradle project has error with unit test #86
- Updating docs to reflect renamed dependency #80
- How to test DHF project that uses multiple databases #74
- Document how to include marklogic-unit-test and set up for a Data Hub #36
Merged pull requests:
- Removing Roxy reference #103 (jamesagardner)
- Updating MarkLogic Copyrights to 2019 #102 (jamesagardner)
- Updating 1.0.beta references to 1.0.0 #101 (jamesagardner)
- Abstract mark logic test logger #99 (hansenmc)
- JaxpServiceResponseUnmarshaller.parse() relies upon default character encoding #98 (hansenmc)
- Update XmlNode.java to use the diamond operator <> #97 (hansenmc)
- change hard-coded namespace-prefix test from name() to use self axis #96 (hansenmc)
- apply $params in xdmp:xslt-invoke() for coverage report format transform #95 (hansenmc)
- Update CONTRIBUTING.md #94 (hansenmc)
- fix AbstractMarkLogicTest.java javadocs #93 (hansenmc)
- Fixing Travis CI error #90 (jamesagardner)
- Fixing Issue #44: assert-equal-json inconsistent in comparisons #85 (cskeefer)
- #79 Updating assertion to be more specific #84 (jamesagardner)
- #79 Fixing module not found error when test module contains the test suite name #83 (jamesagardner)
- Renaming marklogic-junit to marklogic-junit5 #78 (rjrudin)
- Improving the project landing page #73 (jamesagardner)
- bintray config fixes #70 (rjrudin)
- #46 Change test failure stack output from encoded XML to a nested text format #61 (jonesyface)
1.0.beta
Implemented enhancements:
- Support Nested Test Suites #45
- Add Failure Message to Assert Functions #51
- Remove Roxy from Namespaces #52
- Eliminate xdmp:eval() #55
- Allow substitutions during deployment #32
Merged pull requests:
- Merged marklogic-junit library into marklogic-unit-test #66 (rjrudin)
- Specify permissions and collections in test:load-test-file #59 (cskeefer)
- Adding contributor information #50 (jamesagardner)
- Name change from ml-unit-test to marklogic-unit-test #43 (dmcassel)
Breaking Changes:
- The namespaces were updated due to #52 follow these instructions for upgrading.
0.12.0
0.11.1
0.11
Here's the full list of issues.
Note #10 below - the project artifacts are now named "ml-unit-test-client" and "ml-unit-test-modules", and both are available via the main jcenter repository. The ml-gradle sample project has been updated to show how to use these artifacts.
Summary: