We'll show you what to look for, how to find a pull request and how to test the patch. We've created a youtube video showing how to test a patch: Live presentation "Test patch in 3 minutes"

What do I need to test a patch?

And this is how it works:

1st Find Pull Request to test:

The morning of the PBF event, a Google document will be released containing all the patches we would like to test that day. Since this list did not exist when writing the manual, the list of the last PBF is shown here. As soon as there is a current pattern, this graphic is swapped:
Find errors with the PBF event

The list includes:

• Column A: contains the linked patch with color marking (ID = last number).
Green means simple testing with test description.
Yellow means advanced testing ; little or no test description / simple code.
Red means no test description and more extensive code or even writing code.

• Column B: Tester 1 enters their name as soon as they have decided on a patch. After you finish, you will see "done" or "not successfully tested."

• Column C: Tester 2 can work at the same time as Tester 1.

• Column D: This column handles a "Product Owner". This is someone who has the write permission for the source code.

• Hints / issues are posted here if no one can help in the JUG or Glip chat room.

The old list of 2015 ( https: // docs.google.com/spreadsheets/d/1-k-VsUA9enmwtAayr-l5C72-jNPQXqVEFnLi8-IctxY/edit?pli=1#gid=0 ) was with the Issue Tracker ( http://issues.joomla.org ), where you could read the error descriptions .

2. Building the Issue Tracker

Build Issue Tracker
on item 1: For the Using the issue tracker requires a GitHub account. You can visit https://github.com/ Register a GitHub account. When registering, you need Joomla! authorize. Note: If you've enabled Two-Factor Authentication for your GitHub account , you'll need a personal token to access under https://github.com/settings/applications and paste it into the GitHub token field. For more information, see the Patch Tester's Guide .

Github authentication

to point 2: Select language; You can select the German language, but then only the menu items will be displayed in German. Why? Because there is no translator for comments. Please note: Only comment in English, because people from all nations are working on troubleshooting and most of them do not speak German.

to point 3: The search tool; The order can be changed using the filter in the search tools. You can use the "Search Tools" button in the Patch Tester
• for a specific ID
• for the type "issue" or "pull request" (troubleshooting) search for urgent tests.

to point 4: The status is important and is explained here:

New ("new"): The bug has been reported, nothing has been done yet. Immediately after a problem has been reported, it receives this status. So if you find a bug, make a description of how it can be reproduced. Then those who want to test the problem know how to test the patch. Already knew? In Germany there is the possibility with GitHub or via the website https://www.joomla-bugs.de/forum/index.php to report a bug.

Confirmed: The bug has been confirmed, but there is no patch yet. The tracker team was able to understand and replicate the problem. The coding team will now look for a solution.

Pending: There is a patch to fix the bug. A solution to the problem was found. A patch has been created and can be tested. The problem must now be tested. Look for the label next to the title, as it tells you which Joomla! Version of the patch was created.

Simple ("easy"): The patch has sufficient test description to test it without much prior knowledge.

Ready to commit ("RTC"): There's nothing left for us to do, even though the patch is on our list; The patch has been successfully tested and the code can be submitted and will be released soon.

Closed: The patch or bug entry has been closed, for example, because the error could not be fixed or nothing with the Joomla! -Core - but instead For example, with a foreign extension - has to do. The status applies to all issues that do not need further editing. Filtering in Issue Tracker is useful. Monitoring may be useful to receive messages when a problem has been updated. Basically you can edit everything that has the waiting "pending".

5th: The error description; Clicking on the header will explain the mistake. If you decided to fix the problem, then you fix the error on your own installation.

Third: Adjust the error and execute the test description (Issue Tracker)

A list of all the bugs we want to edit at PBF will be distributed on the morning of 08.09.2018. The bugs are using the "Issue Tracker" ( http://issues.joomla.org ) and you get to the error description. If you have authenticated in the patch tester with GitHub, you can use the patch tester, because even in the patch tester you get to the error description. To do this, switch to the Joomla backend in the "Patch Tester" component and search for the error. Normally you can use the search field on the top right to search for the pull ID.

Error description

First, read the bug description (Issue Tracker yellow button) and decide if you can / want to test this patch. After choosing a patch, write your name in the PBF list.

Perform the test description, readjust the bug

Now you log into your Joomla backend and replicate the bug/error in your own Joomla installation. This is an important step, because by adjusting the error, you can check if the bug actually exists (yet).

4th Apply Patch (Patch Tester)

You apply the patch by clicking on the blue button "Apply Patch". The button turns green. The error correction or new feature will automatically be added to your Joomla! - Installation recorded.

If the button "Apply Patch" is hidden, you have to search for the ID in the list.

Apply Patch

The patch has been applied. This means that the program lines which improve the error or contain the new function have been added to your Joomla! Installation. Now you are testing:

  • Is the problem fixed?
  • Does the patch have side effects?
  • Watch the code! Has a file been affected?
  • Please test all affected parts!
  • What else can the patch affect?

5th Take Back Patch (Revert Patch)

After that we will resume the patch with the green button "Revert Patch".

Apply Patch

And after the button turns blue, you get the following message:
patch reverted

6th Comment (Issue Tracker)

Whether the test was successful or unsuccessful it must be logged in the Issue Tracker ( http://issues.joomla.org ). You can either access the page ( http://issues.joomla.org ) to the "Issue Tracker" or via the patch tester by clicking on the yellow "Issue Tracker" button.

If the test was successful or unsuccessful you have to go in Enter Issue Tracker.
Leave feedback:

  • Be honest and to write for example if the code can not be checked, for. Eg "I do not understand the code, but it works"
  • Ask questions in the PBF chat or JUG group
  • Leave a comment in the tracker for questions to the creator of the patch, for an example of what a discussion might look like, see: https://issues.joomla.org/tracker/joomla-cms/21025
  • When the patch has worked, click on the blue "Test this" or "Test" button and select "Successfully tested."

Successfully tested

Here are examples of comment texts

Whether you're a beginner or pro, graphic designer or programmer, whether you have an business or part of a JUG, whether male or female, young or old. We are happy to welcome anyone who already uses Joomla! for work, for fun or only wants to get to know it better. Only the interest in Joomla! counts. Everyone is welcome here.

We would like to invite all Joomla enthusiastic users, no matter what their prior knowledge, to Joomla!. We are grateful for any support! Participation is free, soft drinks and a pizza included.

Did you have any suggestions, additions, find any mistakes or would you like to participate? Would you like to organize a PBF and need support? Then we look forward to receiving your message, contact Benjamin by emailing pbf@benjamintrenkle.de .