tyler.durden/notepad-plus-plus
1
0
Fork 0
mirror of https://github.com/notepad-plus-plus/notepad-plus-plus.git synced 2025-07-27 15:54:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix internal refs

ArkadiuszMichalski 2021-02-23 19:58:28 +01:00
parent 986868e7c2
commit 387ff2a603
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Testing.md

@ -1,6 +1,6 @@
# How to test different versions of Notepad++ #
Before you open a new issue to report a bug, please make sure it's also reproducible in the [latest release of the program](https://github.com/notepad-plus-plus/notepad-plus-plus/wiki/_new#using-the-latest-release-portable-version-of-notepad). If you'd like, you can also test the [current build version](https://github.com/notepad-plus-plus/notepad-plus-plus/wiki/_new#using-the-current-build-version-of-notepad). If the problem is not strictly related to the Notepad ++ installation process (and in the installation version in general) then testing the problem in the portable version is the best solution. Here are the reasons:
Before you open a new issue to report a bug, please make sure it's also reproducible in the [latest release of the program](#using-the-latest-release-portable-version-of-notepad). If you'd like, you can also test the [current build version](#using-the-current-build-version-of-notepad). If the problem is not strictly related to the Notepad ++ installation process (and in the installation version in general) then testing the problem in the portable version is the best solution. Here are the reasons:
- The portable version does not require any installation and runs completely independent and isolated from your installed version. All custom settings, as well as anything you might want to experiment with changing, will not modify your installed version.
- The portable version allows you to quickly determine if the problem is due to incorrect / outdated configuration files (usually located in the user's system folders - [check manual](https://npp-user-manual.org/docs/config-files/)).
@ -26,7 +26,7 @@ notepad.exe -multiInst
## Using the current build version of Notepad++ ##
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++"](https://github.com/notepad-plus-plus/notepad-plus-plus/wiki/_new#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).
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.
4. Click on the blue `Artifacts` link located in the upper right corner.
@ -39,8 +39,8 @@ If the problem still exists in the current build version of Notepad++ then pleas
## Using a Pull-Request (PR) build version of Notepad++ ##
To verify that a specific PR has fixed a bug or implemented a feature, please follow the steps below:
1. Download and extract the latest portable version as described in ["Using the latest-release portable version of Notepad++"](https://github.com/notepad-plus-plus/notepad-plus-plus/wiki/_new#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 page of the PR. If you know the PR number (e.g. 9508) then the link is `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/9508`. The formula to find a link for any PR is to take the base link `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/` and add the PR number to it after the final `/`. If you don't know the PR number, but you know there is one, find the original issue and there should be a way to get to the PR from reading the issue comments.
3. After getting to the page of the PR, click on the `Commits` tab visible on the PR page and you'll be taken to a different page.
4. On this page, locate the bottom-most commit and locate a small green-colored checkmark -- it is actually a link -- to the right of the commit-time; click on it and a small box will open and a `Details` link will be visible; click on that to be taken to a different page.
5. Proceed from the "Click on the job name in the list..." step in the instructions for ["Using the current build version of Notepad++"](https://github.com/notepad-plus-plus/notepad-plus-plus/wiki/_new#using-the-current-build-version-of-notepad) (above).
5. Proceed from the "Click on the job name in the list..." step in the instructions for ["Using the current build version of Notepad++"](#using-the-current-build-version-of-notepad) (above).