---
schema_version: "1"
id: c20bc32d08b4605b402560b378f301340c32459ca7650997dc962a53160236c8
title: Enable Flow Sources
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/munit/3.6/enable-flow-sources-concept.md
canonical_url: https://docs.mulesoft.com/munit/3.6/enable-flow-sources-concept
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d8e2099aec8e9bfa548d2461fbc1c50995cdf43281ee8f6e7d7b3e3d0003ca75
description: MuleSoft Documentation Site
release: "3.6"
latest: false
---
---
product: MUnit
version: 3.6
keywords: munit, test, flow sources
---

# Enable Flow Sources

> 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 `Enable Flow Sources` element within the MUnit test instructs MUnit which flow sources to load
and execute for the test.

By default, MUnit doesn’t start any of the event sources (flow sources such as triggers and
listeners). You must configure which flow sources must start for your tests.

Assume that your application has a flow with an HTTP listener that returns a specific payload:

```xml
<http:listener-config name="HTTP_Listener_config">
    <http:listener-connection host="localhost" port="1234"/>
</http:listener-config>

<flow name="http-example-flow">
    <http:listener path="/" config-ref="HTTP_Listener_config"/>
    <set-payload value="#['Hello World!']" mimeType="text/plain"/>
</flow>
```

For MUnit to invoke that listener, enable the `http-example-flow` in your `enable-flow-source`
property within your MUnit test:

```xml
<http:request-config name="HTTP_Request_config">
    <http:request-connection host="localhost" port="1234"/>
</http:request-config>

<munit:test name="http-example-test">
    <munit:enable-flow-sources>
        <munit:enable-flow-source value="http-example-flow"/>
    </munit:enable-flow-sources>

    <munit:execution>
        <http:request method="GET" path="/" config-ref="HTTP_Request_config"/>
    </munit:execution>

    <munit:validation>
        <munit-tools:assert-that expression="#[payload]"
                                 is="#[MunitTools::equalTo('Hello World!')]"/>
    </munit:validation>
</munit:test>
```

If the `http-example-flow` value isn’t listed as an enabled flow source, your MUnit test fails
because it can’t initialize the HTTP listener configuration.

MUnit starts flow sources at the beginning of the test and stops them at the end of the test. Flow
sources aren’t executed during the before-suite/before-test, nor during the
after-test/after-suite.  
See [Before/After scopes](https://docs.mulesoft.com/munit/3.6/before-after-scopes-reference) for additional information.