Skip to content

GitLab

A
assert-object-equals-module
Commit 7055a58a authored by Danijel Dragicevic's avatar Danijel Dragicevic
Browse files
Options

Add LICENSE

parent ffa304e0
Pipeline #72392 passed with stages
      in 1 minute and 39 seconds
      Show whitespace changes
      Inline Side-by-side
      Showing with 698 additions and 15 deletions
      .gitlab-ci.yml 0 → 100644
      View file @ 7055a58a
      image: maven:latest
      variables:
      MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode"
      MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository"
      cache:
      paths:
      - .m2/repository/
      - target/
      build:
      stage: build
      script:
      - mvn $MAVEN_CLI_OPTS compile
      test:
      stage: test
      script:
      - mvn $MAVEN_CLI_OPTS test
      deploy:
      stage: deploy
      script:
      - mvn $MAVEN_CLI_OPTS deploy
      only:
      - master
      \ No newline at end of file
      .m2/settings.xml 0 → 100644
      View file @ 7055a58a
      <settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd"
      xmlns="http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <servers>
      <server>
      <id>central</id>
      <username>${env.MAVEN_REPO_USER}</username>
      <password>${env.MAVEN_REPO_PASS}</password>
      </server>
      </servers>
      </settings>
      \ No newline at end of file
      LICENSE 0 → 100644
      View file @ 7055a58a
      Apache License
      Version 2.0, January 2004
      http://www.apache.org/licenses/
      TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
      1. Definitions.
      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.
      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.
      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.
      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.
      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.
      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.
      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).
      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.
      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."
      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.
      2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.
      3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.
      4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:
      (a) You must give any other recipients of the Work or
      Derivative Works a copy of this License; and
      (b) You must cause any modified files to carry prominent notices
      stating that You changed the files; and
      (c) You must retain, in the Source form of any Derivative Works
      that You distribute, all copyright, patent, trademark, and
      attribution notices from the Source form of the Work,
      excluding those notices that do not pertain to any part of
      the Derivative Works; and
      (d) If the Work includes a "NOTICE" text file as part of its
      distribution, then any Derivative Works that You distribute must
      include a readable copy of the attribution notices contained
      within such NOTICE file, excluding those notices that do not
      pertain to any part of the Derivative Works, in at least one
      of the following places: within a NOTICE text file distributed
      as part of the Derivative Works; within the Source form or
      documentation, if provided along with the Derivative Works; or,
      within a display generated by the Derivative Works, if and
      wherever such third-party notices normally appear. The contents
      of the NOTICE file are for informational purposes only and
      do not modify the License. You may add Your own attribution
      notices within Derivative Works that You distribute, alongside
      or as an addendum to the NOTICE text from the Work, provided
      that such additional attribution notices cannot be construed
      as modifying the License.
      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.
      5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.
      6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.
      7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.
      8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.
      9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.
      END OF TERMS AND CONDITIONS
      APPENDIX: How to apply the Apache License to your work.
      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "{}"
      replaced with your own identifying information. (Don't include
      the brackets!) The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.
      Copyright 2019 Danijel Dragicevic
      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at
      http://www.apache.org/licenses/LICENSE-2.0
      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.
      README.md
      View file @ 7055a58a
      ......@@ -5,29 +5,42 @@ Mule 4.x (tested on 4.1.4 version)
      In case you are working with Mule 3.x, have a look [here](https://github.com/rbutenuth/assert-object-equals-connector), there you find a version suitable for Mule 3.
      ## Installation
      For beta connectors you can download the source code and build it with Maven (mvn clean install).
      Then you can add it to Studio by adding the following dependency to your project:
      ```
      <groupId>de.codecentric.mule.modules</groupId>
      <artifactId>assert-object-equals-module</artifactId>
      <version>1.0.180-SNAPSHOT</version>
      <classifier>mule-plugin</classifier>
      To install this module via Maven, please add following repository and dependency to yur pom.xml file
      ```xml
      <repository>
      <id>central</id>
      <name>artifactory.codecentric.de-releases</name>
      <url>https://artifactory.codecentric.de/artifactory/public</url>
      </repository>
      <dependency>
      <groupId>de.codecentric.mule.modules</groupId>
      <artifactId>assert-object-equals-module</artifactId>
      <version>1.1.0</version>
      <classifier>mule-plugin</classifier>
      </dependency>
      ```
      ## Usage
      Documentation will be released soon.
      The connector can be used for Object structures or XML:
      ## CI
      * [Object structures and JSON](../docs/compare-objects.md)
      * [XML](../docs/compare-xml.md)
      Will be added later....
      ## Mule example app
      ## Maven Site
      Mule 4 example application can be checked out here:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equal-module-mule-app-example
      ## CI
      Will be added later....
      Pipelines for this project:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/pipelines?scope=branches&page=1
      ## Reporting Issues
      We use GitLab: Issues for tracking issues with this connector. You can report new issues at this link https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/issues.
      \ No newline at end of file
      We use GitLab Issues for tracking issues with this connector. You can report new issues at this link:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/issues.
      \ No newline at end of file
      docs/compare-objects.md 0 → 100644
      View file @ 7055a58a
      # Comparing Objects (or JSON)
      The object comparison is 'hand written' and not based on an existing library. So be careful, there may be bugs. :-)
      It can be used to compare object structures the way Mule uses, nested Java `List` and `Map` (or anything else with
      a meaningful `equals()` methods, but for this you don't need this connector).
      The actual value and the comparison value (called expected) can be provided as object structure or in one of the follogin ways:
      * InputStream
      * byte[]
      * OutputHandler (returned by DataWeav with mode="deferred")
      * String starting with `[` or `{`
      All these will be converted to an object structure by `org.codehaus.jackson.map.ObjectMapper`. Since version 1.0.0 the operation does no longer return the parsed object, it now returns the input object (in case of InputStream/OutputHandler: A copy because the stream has to be read to do the comparison).
      The test for equality will drill down the object structure:
      * `null` equals `null`
      * Two maps are equal when they contain the same key set and the mapping is equal for map entries with the same key in the two maps.
      * Two lists are equal when they have the same size and elements with same index are equal in the two lists.
      * Other objects are equal according their `equals()` method.
      ## Options
      There are three options to tweak the comparison. They can be set globally (two of them) or on sub trees:
      1. `contains_only_on_maps`: Two maps are considered equal, when the key set of the expected map is a subset of the key set of the actual map.
      (Of course, values must still be equal.) This option is useful when you want to check that some values are contained in the result.
      2. `check_map_order`: This confines the comparison of the key sets of map: They must be equal and in the same order. This makes
      no sense for `HashMap`, but for `LinkedHashMap` (which is used by Mule in a lots of places).
      3. `ignore`: The node is ignored in the comparison. Useful to exclude values like time stamps or sequence numbers from the comparison.
      For obvious reasons this option is not available on the global level.
      ## Path patterns
      When you want to apply one (or several) of this options to a subtree of the object structure, you have to specify the path to the subtree
      by one of the following patterns:
      * `?` (wildcard one): Matches one node in the tree (Map, List, leaf).
      * `*` (wildcard any): Matches a sequence of nodes (can be the empty sequence).
      * `[#]`: Matches a List element.
      * `[42]` Matches List element with index 42 (starting at 0).
      * `[-1]` Matches the last element in a List (-2 for the second last etc.).
      * `['foo']` Matches the Map entry `foo`. The String between the single quotes is a regular expression.
      * `['fo''o']` Matches the Map entry `fo'o` (example for quoting).
      * `['foo.*']` Matches all Map entries starting with `foo` (example for the regular expression feature).
      The path patterns can be combined, e.g.:
      ```['addresses'][#]['street']```
      Matches the node `street` for each address in a list of addresses in the node `addresses`.
      After the path pattern you can place one or several options shown above (separated by space).
      ## Examples
      So let's look at some examples. I have created two JSON documents:
      The expected JSON document:
      ```json
      {
      "name": "Peter Pan",
      "addresses": [
      {
      "timestamp": 4711,
      "street": "Elm Street",
      "city": "New York"
      },
      {
      "timestamp": 4712,
      "street": "Hochstraße",
      "city": "Solingen"
      }
      ],
      "profession": "Wizard"
      }
      ```
      The actual JSON document:
      ```json
      {
      "name": "Peter Pan",
      "profession": "Wizard",
      "addresses": [
      {
      "street": "Elm Street",
      "timestamp": 1234,
      "city": "New York"
      },
      {
      "timestamp": 1235,
      "street": "Hochstraße",
      "city": "Solingen"
      }
      ]
      }
      ```
      When you look at them closely, you will find some differences:
      1. The order of the top level object is different (addresses/profession)
      2. The timestamp in the addresses is different
      3. The order within the addresses objects is different
      Our first try will throw an `AssertionError` because of different timestamp values:
      ```xml
      <munit:test name="compare-person-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      I marked the exception as expected, so the test itself will be green. (Nobody likes red bars...)
      To make the object structures equal for this module, we have to exclude the timestamp from the comparison.
      The first way to do this is with an embedded object:
      ```xml
      <munit:test name="compare-person-success-1-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]">
      <assertobjectequals:path-options >
      <assertobjectequals:path-option value="['addresses'][#]['timestamp'] ignore" />
      </assertobjectequals:path-options>
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      We can configure this in the GUI by clicking on the "Path patterns + options" drop-down menu and selecting "Edit inline" option.
      After that we have to click on green plus sign to add our path option. Popup window will open, and allow us to enter our value.
      See the picture bellow:
      ![Object Builder](../docs/images/object-builder.png)
      Another way is to express the list as a MEL expression:
      ```xml
      <munit:test name="compare-person-success-2-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      How can we fail in a different way? Activate Map order checking:
      ```xml
      <munit:test name="compare-person-fail-map-order-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]"
      checkMapOrder="true">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      For a complete example of the test suite see [object-demos.xml](object-demos.xml).
      docs/compare-xml.md 0 → 100644
      View file @ 7055a58a
      # Comparing XML
      The XML comparison is based on [xmlunit](https://github.com/xmlunit/xmlunit), version 2.3.0.
      For the demos in this documentation, I provided the XML as String in MEL expressions. This works only for really small XML
      and the escaping of `<` and `>` makes it completely unreadable when you switch to the XML view in AnypointStudio.
      Fortunately, xmlunit is quite flexible when it comes to input sources: It can consume Strings (as in the examples), byte arrays, InputStreams,
      Files and some more sources. See [xmlunit documentation](https://github.com/xmlunit/user-guide/wiki/Providing-Input-to-XMLUnit) for details.
      If you have bigger XML documents, place them in `src/test/resources` and load them with `getResourceAsString(...)`, e.g. like this:
      ```txt
      "#[MunitTools::getResourceAsString('xml/simple-expected.xml')]"
      ```
      ## Simple example
      So let's start with a simple example to compare two XML Strings:
      ![xml-is-xml](../docs/images/xml-is-xml.png)
      As long as you ignore all the quoting, it's quite simple in XML, too:
      ```xml
      <munit:test name="compare-xml" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="xml is xml"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      ```
      ## Handling whitespace and comments
      Usually we don't want to compare our XML documents character by character, otherwise we could just use the built in assert of MUnit.
      We can select between three modes of comparison:
      * NORMALIZE_WHITESPACE : Normalize Text-Elements by removing all empty text nodes and normalizing the non-empty ones.
      * IGNORE_WHITESPACE: Ignore whitespace by removing all empty text nodes and trimming the non-empty ones.
      * IGNORE_COMMENTS: Will remove all comment-Tags "<!-- Comment -->" from test- and control-XML before comparing.
      "normalized" in this context means all whitespace characters are replaced by space characters and consecutive
      whitespace characters are collapsed.
      For a complete example of the test suite see [xml-demos.xml](xml-demos.xml).
      docs/object-demos.xml 0 → 100644
      View file @ 7055a58a
      <?xml version="1.0" encoding="UTF-8"?>
      <mule
      xmlns:assertobjectequals="http://www.mulesoft.org/schema/mule/assertobjectequals"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:munit="http://www.mulesoft.org/schema/mule/munit"
      xmlns:munit-tools="http://www.mulesoft.org/schema/mule/munit-tools"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
      xsi:schemaLocation="
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
      http://www.mulesoft.org/schema/mule/munit http://www.mulesoft.org/schema/mule/munit/current/mule-munit.xsd
      http://www.mulesoft.org/schema/mule/munit-tools http://www.mulesoft.org/schema/mule/munit-tools/current/mule-munit-tools.xsd
      http://www.mulesoft.org/schema/mule/assertobjectequals http://www.mulesoft.org/schema/mule/assertobjectequals/current/mule-assertobjectequals.xsd">
      <munit:config name="object-demos" doc:name="Munit configuration" />
      <munit:test name="compare-strings-success-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (foo is foo)"
      expected="#['foo']"
      actual="#['foo']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-strings-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test">
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="fails (foo is not bar)"
      expected="#['foo']"
      actual="#['bar']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-expected-from-resource-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (foo is foo)"
      expected="#[MunitTools::getResourceAsString('json/simple-expected.json')]"
      actual="#['{&quot;foo&quot;: 42}']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="fails (timestamp)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-success-1-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]">
      <assertobjectequals:path-options >
      <assertobjectequals:path-option value="['addresses'][#]['timestamp'] ignore" />
      </assertobjectequals:path-options>
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-success-2-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in MEL)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-map-order-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]"
      checkMapOrder="true">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-contains-only-on-maps-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-extended.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      containsOnlyOnMaps="true">
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      </mule>
      docs/xml-demos.xml 0 → 100644
      View file @ 7055a58a
      <?xml version="1.0" encoding="UTF-8"?>
      <mule
      xmlns:assertobjectequals="http://www.mulesoft.org/schema/mule/assertobjectequals"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:munit="http://www.mulesoft.org/schema/mule/munit"
      xmlns:munit-tools="http://www.mulesoft.org/schema/mule/munit-tools"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
      xsi:schemaLocation="
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
      http://www.mulesoft.org/schema/mule/munit http://www.mulesoft.org/schema/mule/munit/current/mule-munit.xsd
      http://www.mulesoft.org/schema/mule/munit-tools http://www.mulesoft.org/schema/mule/munit-tools/current/mule-munit-tools.xsd