Skip to content

Releases: marklogic-community/marklogic-unit-test

1.4.0

08 Sep 18:18
4681ba2
Compare
Choose a tag to compare

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 its mlUnitTest 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 of null, 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

07 Feb 20:12
Compare
Choose a tag to compare

This minor release addresses the following items:

  • #150 Added support for tests written as .mjs modules
  • Bumped the Java Client dependency to 6.1.0
  • Updated documentation for getting started
  • Updated documentation that lists all available assertion functions

1.2.1

22 Aug 13:51
52d139d
Compare
Choose a tag to compare

This is a bugfix release that updates most dependencies to their latest release to minimize security vulnerabilities:

1.2.0

14 Apr 13:44
bf6c7d0
Compare
Choose a tag to compare

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

22 Jul 18:35
Compare
Choose a tag to compare

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

13 Sep 18:26
63a8aa4
Compare
Choose a tag to compare

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:

  • Unable to use suite name in test name #79
  • JSON equals is inconsistent in comparisons #44

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:

1.0.beta

26 Apr 20:36
1b1a26a
Compare
Choose a tag to compare
1.0.beta Pre-release
Pre-release

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:

0.12.0

20 Sep 21:28
571fb29
Compare
Choose a tag to compare

Project name changed from ml-unit-test to marklogic-unit-test, which also led to some directory name changes.

0.11.1

05 Jun 14:49
Compare
Choose a tag to compare

0.11

22 May 15:04
Compare
Choose a tag to compare

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:

  • #4 The UI test runner now provides an option for calculating code coverage
  • #1 Alternative report formats are supported via user-defined transforms
  • #10 The project was reorganized so that the MarkLogic modules are in one Gradle subproject and the Java client is in a separate subproject