---
schema_version: "1"
id: 87116e23eba5bc31a338ec44dd7b9ea34c93a14335337662c2d9a5bdf124e718
title: Assert Equals
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/munit/3.6/assertion-equals-processor.md
canonical_url: https://docs.mulesoft.com/munit/3.6/assertion-equals-processor
source_site: docs.mulesoft.com
content_type: documentation
content_hash: da6aa8e4026d8e19e959d3d907a000a95f6dd74f0faab818fb3f497c2b6273c4
description: MuleSoft Documentation Site
release: "3.6"
latest: false
---
---
product: MUnit
version: 3.6
---

# Assert Equals

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

![logo acb active](/mulesoft/current/en-us/_/img/icons/anypoint-code-builder.svg "Anypoint Code Builder")Anypoint Code
Builder

![logo studio active](/mulesoft/current/en-us/_/img/icons/studio.svg "Anypoint Studio")Anypoint Studio

The Assert Equals processor allows you to run assertions in order to validate the state of a Mule
Event’s content. This processor can be used to validate the Mule Event after the production code
runs.

For example, to assert that a payload is equal to a certain value, you can configure the
Assert-Equals processor the following way:

```xml
<munit-tools:assert-equals
  actual="#[payload]"
  expected="#[2]"
  message="The payload should be 2"/>
```

If the `expected` attribute is a String, you can specify the literal value without requiring an
expression.

```xml
<munit-tools:assert-equals
  actual="#[payload]"
  expected="Example"
  message="The payload should be 'Example'"/>
```

If this assertion fails, the processor throws a `java.lang.AssertionError`.