---
schema_version: "1"
id: ec1be745c7b9459ecd1082e9b8cf1c9dd599cea9f8403b7244e3425c72a6655b
title: MUnit Verify Event Processor
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/munit/latest/verify-event-processor.md
canonical_url: https://docs.mulesoft.com/munit/latest/verify-event-processor
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b912c4511ec507abb1a4923d299b3b5913c0f35abd6e1c61f58751b4f251869c
description: MuleSoft Documentation Site
release: "3.7"
latest: true
---
---
product: MUnit
version: 3.7
is-latest-version: true
keywords: munit, testing, unit testing
---

# MUnit Verify Event Processor

> 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 MUnit Verify event processor validates that a specified event processor was called a certain
number of times during a MUnit test. Use it to confirm that your flow executed the expected
processors with the expected attributes, even without creating a mock for them.

```xml
<munit-tools:verify-call processor="http:request" atLeast="1">
   <munit-tools:with-attributes>
       <munit-tools:with-attribute attributeName="method" whereValue="#['GET']" />
   </munit-tools:with-attributes>
</munit-tools:verify-call>
```

<table><colgroup><col> <col></colgroup><thead><tr><th>Attribute Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>eventProcessor</code></p></td><td><p>Describes which event processor you want to mock. The description takes the form <code>{name-space}:{event-processor-name}</code>. It supports regular expressions.</p></td></tr><tr><td><p><code>times</code></p></td><td><p><strong>(Default = 1.)</strong> Defines the verification as successful if the event processor was called <em>N</em> and only <em>N</em> number of times.</p></td></tr><tr><td><p><code>atLeast</code></p></td><td><p>Defines the verification as successful if the event processor was called a minimum of <em>N</em> number of times.</p></td></tr><tr><td><p><code>atMost</code></p></td><td><p>Defines the verification as successful if the event processor was called maximum of <em>N</em> number of times.</p></td></tr></tbody></table>

The attributes `times`, `atLeast`, `atMost`, are mutually exclusive.

The `eventProcessor` attribute accepts regular expressions. For example, you can create the same
verification as `.*:request` to verify for an event processor named request, disregarding which
namespace the event processor belongs to. The regular expression language is the same as Java.

## See Also

- [Assert That Event Processor](https://docs.mulesoft.com/munit/latest/assertion-event-processor)

- [Fail Event Processor](https://docs.mulesoft.com/munit/latest/fail-event-processor)

- [Run Custom Event Processor](https://docs.mulesoft.com/munit/latest/run-custom-event-processor)

- [Set Event Processor](https://docs.mulesoft.com/munit/latest/set-event-processor)

- [Mock When Event Processor](https://docs.mulesoft.com/munit/latest/mock-event-processor)