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

# 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 Verify Event processor allows you to verify if a processor was called.

For example, you can validate if a specific processor has been called with a particular set of
attributes a specific number of times.

When defining a verification, you are telling MUnit to fail a test if the verification is not
successful.

You can define verifications over any processor, even if you haven’t created a mock for it.

```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/3.6/assertion-event-processor)

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

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

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

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