Project

General

Profile

LoadingTestModules » History » Version 9

Dan Smith, 06/30/2023 07:06 PM

1 1 Dan Smith
# How to load test modules
2
3 7 Dan Smith
If a CHIRP developer tells you to load a module to test, follow these instructions.
4 1 Dan Smith
5 5 Dan Smith
1. Launch CHIRP. Make sure you are running the latest CHIRP-next build. If not, upgrade and start over.
6
2. Click **Help** in the menu bar and select **Load module from issue**
7 8 Dan Smith
3. Key in the Issue number which has the test module attached (see below) and click the **[OK]** button
8 4 Dan Smith
4. Select the driver module listed and click the **[OK]** button. If there are multiple modules attached, select the one the developer wants you to test, usually the latest/last one.
9 6 Dan Smith
Your CHIRP is now running with the test driver module loaded.
10
5. Test and report back your results. Be sure to **include a debug log** per the [[How_To_Report_Issues|instructions here]].
11 2 Dan Smith
12 1 Dan Smith
**Note:** An externally loaded driver module like this does not permanently change your CHIRP installation in any way. Once you close CHIRP you will have to re-load the driver module in order to have the added fixes or features again.
13 8 Dan Smith
14
## Finding the issue number
15
16
The issue number that you need to put into chirp is on the page where you are communicating with the developer. In the example below, the issue number is `10672`:
17
18
<img src="issue_screen.png" height="300"/>
19 9 Dan Smith
20
You would enter this number into CHIRP in the following way:
21
22
<img src="issue_entry.png" height="300"/>