CHIRP

# How to load test modules

If a chirp developer tells you to load a module to test, follow these instructions.

**NOTE:** Loading a module can cause data corruption and or execute code on your system. Only load modules from trusted sources and use extreme care when using this functionality!

## Enable Developer Mode

In the **Help** menu, select **Enable Developer Mode** so that it is checked.

<img src="enable_developer.png" width="300"/>

You will see the following notice:

<img src="developer_mode.png" width="300"/>

**NOTE:** You must exit and re-start CHIRP at this point for Developer Mode to be fully active.

## Load the module

With Developer Mode enabled, a new entry in the **File** menu named **Load Module** will be present. Select this and then choose the module file to be loaded.

<img src="load_module.png" width="300"/>

**NOTE:** The module is only loaded while CHIRP is running. If you exit CHIRP and restart, you will need to load the module again for the changes to be active.

## Reproduce the issue

Once the module is loaded, test the behavior in question, reproduce the issue, etc. Then _before you exit CHIRP_ capture a debug log. See [[How_to_report_issues]] for details about capturing a debug log.

## Finishing up

Once you are done testing the new module, it is recommended that you put CHIRP back to normal by going back to the **Help** menu an uncheck **Developer Mode**.