Project

General

Profile

LoadingTestModules » History » Version 3

Dan Smith, 02/27/2023 05:01 PM

1 1 Dan Smith
# How to load test modules
2
3
If a chirp developer tells you to load a module to test, follow these instructions.
4
5
**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!
6
7
## Enable Developer Mode
8
9
In the **Help** menu, select **Enable Developer Mode** so that it is checked.
10
11 3 Dan Smith
<img src="enable_developer.png" width="50%"/>
12 1 Dan Smith
13
You will see the following notice:
14
15 3 Dan Smith
<img src="developer_mode.png" width="50%"/>
16 1 Dan Smith
17 3 Dan Smith
**NOTE:** You must exit and restart CHIRP at this point for Developer Mode to be fully active.
18 1 Dan Smith
19
## Load the module
20
21
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.
22
23 3 Dan Smith
<img src="load_module.png" width="50%"/>
24 1 Dan Smith
25
**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.
26
27
## Reproduce the issue
28
29
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.
30 2 Dan Smith
31
## Finishing up
32
33
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**.