The document explains the 'run and wait' scope in MUnit, which allows for waiting until all asynchronous executions are completed before starting test execution. It highlights the importance of validating results from threads launched by production code and provides a basic implementation approach. Additionally, it mentions an implementation using Java API by extending the synchronizer abstract class.

1. MUNIT
RUN AND WAIT SCOPE
Shanky Gupta

2. FUNCTIONALITY
The Run and Wait scope provided by MUnit allows you to instruct
MUnit to wait until all asynchronous executions have completed.
Hence, test execution does not start until all threads opened by
production code have finished processing.

3. DEFINING RUN AND WAIT
In some cases, your production code may launch threads that produce key
results. Usually, these are the results that you want to validate. But if those
results are being processed in a separate thread, your test runs and finishes
before that separate thread completes, that is, before the results that you
want to validate are available. To avoid this problem, you can use the run-
and-wait scope.
For the purposes of this presentation, we assume that we are testing the
Mule code in following slides:

4. Visual Editor view
XML code

6. The goal is to make your test wait until the exampleFlow has finished.
To do so, implement the test as shown below.

7. 1. Define run-and-wait scope.
2. Call the actual production code to test.

8. DEFINING RUN AND WAIT WITH
JAVA CODE
Java API usage
To define the run-and-wait scope in Java, you need to
implement the Synchronizer abstract class, as shown in the
next slide: