Updated Testing (markdown)

sasumner 2021-04-17 07:54:17 -04:00
parent 21ae89ba33
commit 0e86ede9e1

@ -28,9 +28,9 @@ notepad.exe -multiInst
To make sure that the bug you are reporting has not been fixed in the current-build version please follow the steps below: To make sure that the bug you are reporting has not been fixed in the current-build version please follow the steps below:
1. Download and extract the latest portable version as described in ["Using the latest-release portable version of Notepad++"](#using-the-latest-release-portable-version-of-notepad) (above). 1. Download and extract the latest portable version as described in ["Using the latest-release portable version of Notepad++"](#using-the-latest-release-portable-version-of-notepad) (above).
2. Go to the [official current-build page](https://ci.appveyor.com/project/donho/notepad-plus-plus). 2. Go to the [official current-build page](https://ci.appveyor.com/project/donho/notepad-plus-plus).
3. Click on the `Job name` in the list for the `Unicode Debug` job compatible with your version of Notepad ++ (`platform = Win32` for 32-bit Notepad++ or `platform = x64 for 64-bit Notepad++`). Ignore completely the `mingw` build jobs, and the `Unicode Release` jobs. 3. Click on the `Job name` in the list for the `Unicode Debug` job compatible with your version of Notepad ++ (`platform = Win32` for 32-bit Notepad++ or `platform = x64 for 64-bit Notepad++`). Ignore completely the `mingw` build jobs, the `Unicode Release` jobs, and probably the `amd64` jobs (unless you know you need that) .
4. Click on the blue `Artifacts` link located in the upper right corner. 4. Click on the blue `Artifacts` link located in the upper right corner.
5. Download the appropriate `.exe` file (depending on step 3, it will be either `Notepad++.Win32.Unicode Debug.exe` or `Notepad++.x64.Unicode Debug.exe`). Note that although a `.dll` file is provided, it is typically not necessary to obtain this file<!-- ([check details](#using-a-different-version-of-scilexerdll-file))-->. 5. Download the appropriate `.exe` file (depending on step 3, it will be either `Notepad++.Win32.Debug.exe` or `Notepad++.x64.Debug.exe`).
6. Add this `.exe` file to your portable Notepad++ folder and start the program with this executable instead of the normal `notepad++.exe` that is present in this folder. 6. Add this `.exe` file to your portable Notepad++ folder and start the program with this executable instead of the normal `notepad++.exe` that is present in this folder.
7. Try to reproduce the problem in this current-build version. 7. Try to reproduce the problem in this current-build version.