Joomla! Documentation - User contributions [en]

Testing Joomla! patches/ru

2023-10-05T18:08:26Z

Jevsystems: Created page with "'''Закрыто''' - этот статус присваивается всем вопросам, не требующим дальнейших действий."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков будет искать решение.

'''Ожидается''' - Решение проблемы найдено. Приложен патч, который можно протестировать. Проблема нуждается в тестировании. Обратите внимание на метку рядом с заголовком, она указывает, для какой версии Joomla применимо исправление.

'''Готов к принятию''' - патч успешно протестирован, и код может быть зафиксирован.

'''Закрыто''' - этот статус присваивается всем вопросам, не требующим дальнейших действий.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/16/ru

2023-10-05T18:08:25Z

Jevsystems: Created page with "'''Закрыто''' - этот статус присваивается всем вопросам, не требующим дальнейших действий."

'''Закрыто''' - этот статус присваивается всем вопросам, не требующим дальнейших действий.

Testing Joomla! patches/ru

2023-10-05T18:07:21Z

Jevsystems: Created page with "'''Готов к принятию''' - патч успешно протестирован, и код может быть зафиксирован."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков будет искать решение.

'''Ожидается''' - Решение проблемы найдено. Приложен патч, который можно протестировать. Проблема нуждается в тестировании. Обратите внимание на метку рядом с заголовком, она указывает, для какой версии Joomla применимо исправление.

'''Готов к принятию''' - патч успешно протестирован, и код может быть зафиксирован.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/15/ru

2023-10-05T18:07:13Z

Jevsystems: Created page with "'''Готов к принятию''' - патч успешно протестирован, и код может быть зафиксирован."

'''Готов к принятию''' - патч успешно протестирован, и код может быть зафиксирован.

Testing Joomla! patches/ru

2023-10-05T18:06:14Z

Jevsystems: Created page with "'''Ожидается''' - Решение проблемы найдено. Приложен патч, который можно протестировать. Проблема..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков будет искать решение.

'''Ожидается''' - Решение проблемы найдено. Приложен патч, который можно протестировать. Проблема нуждается в тестировании. Обратите внимание на метку рядом с заголовком, она указывает, для какой версии Joomla применимо исправление.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/14/ru

2023-10-05T18:06:11Z

'''Ожидается''' - Решение проблемы найдено. Приложен патч, который можно протестировать. Проблема нуждается в тестировании. Обратите внимание на метку рядом с заголовком, она указывает, для какой версии Joomla применимо исправление.

Testing Joomla! patches/ru

2023-10-05T18:05:41Z

Jevsystems: Created page with "'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков будет искать решение.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/13/ru

2023-10-05T18:05:38Z

'''Подтверждено''' - Команда разработчиков смогла воспроизвести проблему. Команда разработчиков будет искать решение.

Testing Joomla! patches/ru

2023-10-05T18:04:55Z

Jevsystems: Created page with "'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки со..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/12/ru

2023-10-05T18:04:54Z

'''Новое''' - сразу после сообщения о проблеме она получает этот статус. При обнаружении ошибки создайте описание того, как ее воспроизвести. Тогда люди, тестирующие проблему, будут знать, как тестировать патч.

Testing Joomla! patches/ru

2023-10-05T18:03:25Z

Jevsystems: Created page with "Статус важен, а это объяснение:"

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Статус важен, а это объяснение:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/11/ru

2023-10-05T18:03:24Z

Jevsystems: Created page with "Статус важен, а это объяснение:"

Статус важен, а это объяснение:

Testing Joomla! patches/ru

2023-10-05T18:03:24Z

Jevsystems: Created page with "В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/10/ru

2023-10-05T18:03:07Z

В будущем эти обозначения будут меняться по мере появления новых и исчезновения старых версий.

Testing Joomla! patches/ru

2023-10-05T18:02:57Z

Jevsystems: Created page with "Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильт..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/9/ru

2023-10-05T18:02:49Z

Список показывает элементы трекера от новых к старым, но порядок можно изменить с помощью фильтров в разделе Инструменты поиска. Все элементы трекера, имеющие патч, имеют номер версии рядом с названием.
* PR-staging: Это Joomla 3.9.x
* PR-4.0-dev: Это Joomla 4.0

Testing Joomla! patches/ru

2023-10-05T18:02:01Z

Jevsystems: Created page with "ru"

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-ru.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/8/ru

2023-10-05T18:01:58Z

Jevsystems: Created page with "ru"

Testing Joomla! patches/ru

2023-10-05T18:01:29Z

Jevsystems:

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Трекер отслеживания ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/6/ru

2023-10-05T18:01:24Z

Jevsystems:

=== Трекер отслеживания ошибок ===

Testing Joomla! patches/ru

2023-10-05T18:01:18Z

Jevsystems: Created page with "Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Отслеживание ошибок ===
Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/7/ru

2023-10-05T18:01:12Z

Jevsystems: Created page with "Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org."

Трекер отслеживания ошибок для Joomla находится здесь: https://issues.joomla.org.

Testing Joomla! patches/ru

2023-10-05T18:00:25Z

Jevsystems: Created page with "=== Отслеживание ошибок ==="

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== Отслеживание ошибок ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/6/ru

2023-10-05T18:00:24Z

Jevsystems: Created page with "=== Отслеживание ошибок ==="

=== Отслеживание ошибок ===

Testing Joomla! patches/ru

2023-10-05T17:59:10Z

Jevsystems: Created page with "Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

=== The issue-tracker ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/5/ru

2023-10-05T17:59:10Z

Код разработки Joomla находится по адресу https://github.com/joomla/joomla-cms, именно его необходимо установить. О том, как это делается, рассказано чуть дальше в разделе [[#Preparing to test|Подготовка к тестированию]].

Testing Joomla! patches/ru

2023-10-05T17:59:05Z

Jevsystems:

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].

=== The issue-tracker ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/4/ru

2023-10-05T17:59:00Z

Jevsystems:

Код разработки Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Testing Joomla! patches/ru

2023-10-05T17:58:54Z

Jevsystems:

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код разработки Joomla ===
Постановочный код Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].

=== The issue-tracker ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/3/ru

2023-10-05T17:58:51Z

Jevsystems:

=== Код разработки Joomla ===

Testing Joomla! patches/ru

2023-10-05T17:54:52Z

Jevsystems: Created page with "Постановочный код Joomla - это самый последний код, над которым ведется работа. Все исправления и н..."

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код постановки Joomla ===
Постановочный код Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].

=== The issue-tracker ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/4/ru

2023-10-05T17:54:50Z

Постановочный код Joomla - это самый последний код, над которым ведется работа. Все исправления и новые возможности применяются к этому коду.

Testing Joomla! patches/ru

2023-10-05T17:50:07Z

Jevsystems: Created page with "=== Код постановки Joomla ==="

<noinclude><languages /></noinclude>
В любом программном обеспечении есть ошибки, требующие исправления. Это относится и программному обеспечению с открытым исходным кодом, такому, как Joomla!. Исходный код Joomla! располагается в сети Интернет централизованно, что делает его доступным для всех. Любой, кто обнаружит баг или проблему с Joomla!, может о них сообщить. Руководство для сообщений об ошибках можно найти здесь: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]] Найденные ошибки будут исправлены и в конечном итоге нуждаются в тестировании.

=== Код постановки Joomla ===
The Joomla staging code is the most recent code that is being worked on. All bugfixes and new features are applied to this code.

The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].

=== The issue-tracker ===
The issue-tracker for Joomla is located here: https://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0

These labels will change in the future as new versions come and old versions go.

The status is important and this is an explanation:

'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description of how to reproduce the bug. People who are testing the issue then know how to test the patch.

'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.

'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.

'''Ready to commit''' - The patch has been successfully tested and the code can be committed.

'''Closed''' - This status is for all issues that need no further action.

Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.

Basically you start testing issues that have the status "Pending".

=== Preparing to test ===
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.

==== Create folder ====
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.

==== Download Joomla! ====
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''

[[File:joomla_github-en.png]]

This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data

This is important so everybody uses the same data to test!

The installation folder does not have to be removed, this way you can easily reinstall everything if needed.

=== Download Patch Tester ===
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page]

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].

=== Setup Patch Tester ===
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.

[[File:patchtester_repo-en.png]]

On the second tab called GitHub Authentication you can enter your GitHub username and a personal access token as password.

[[File:Joomla PatchTester Github credentials.png|800px]]

After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.

You are now ready to start testing.

Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.

=== Installing Patch ===
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced

=== Recording test results ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revert patch ===
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/3/ru

2023-10-05T17:50:05Z

Jevsystems: Created page with "=== Код постановки Joomla ==="

=== Код постановки Joomla ===

Testing Joomla! patches/es

2023-10-05T17:47:13Z

Jevsystems:

<noinclude><languages /></noinclude>
<div class="mw-translate-fuzzy">
En todo el software hay errores que deben ser corregidos, este es también el caso en un software de código Abierto como Joomla!. El código fuente de Joomla está situado en la internet, por lo que es accesible a todo el mundo. Además hay una posibilidad para el informe de errores. Los errores reportados serán resueltos y eventualmente necesitara de pruebas. Esta página se explica de qué manera puede contribuir al proyecto Joomla con las pruebas de las soluciones propuestas. Usted no necesita tener ningún conocimiento de codificación, usted no necesita una instalación de Joomla para hacer pruebas.
Una Guía de Referencia Rápida para las pruebas está disponible en: [[S:MyLanguage/Testing Joomla! patches QuickReferenceGuide|Guía de Referencia Rápida para Pruebas de parches en Joomla!]]
</div>

=== El código de ensayo en Joomla ===
El código de ensayo de Joomla es el código más reciente en el que se está trabajando. Todas las correcciones de errores y nuevas características se aplican a este código.

El código de ensayo de Joomla lo encontrará en https://github.com/joomla/joomla-cms, este es el código que necesita instalarse. Encontrará la explicación de cómo hacerlo un poco más adelante [[#Preparing to test|Preparación de la prueba]].

=== El gestor de incidencias ===
El gestor de incidencias de Joomla está en: http://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

Esta lista muestra los errores que están en el tracker en un listado que va del más nuevo al más antiguo, pero puedes cambiar el orden mediante los filtros, en herramientas de búsqueda. En el tracker, todos los errores que tienen un parche, tienen un número de versión junto al título.
* PR-staging: Para Joomla 3.9.x
* PR-4.0-dev: Para Joomla 4.0

Estas etiquetas cambiarán en el futuro a medida que cambien las versiones.

Es importante tener en cuenta el Estado, seguidamente se da una explicación sobre el significado de cada estado:

'''Nuevo''' - Inmediatamente después de que se informa de un problema, recibe este estado. Cuando encuentre un error, cree una descripción de cómo reproducir el error. Las personas que están probando el problema deben de saber cómo probar el parche.

'''Confirmado''' - El equipo de seguimiento ha sido capaz de reproducir el problema. El equipo de codificación va a buscar una solución.

'''Pendiente''' - se ha encontrado una solución al problema. Se ha adjuntado el parche para que pueda probarse. Necesita probarse el problema. Se ha de prestar atención a la etiqueta junto al título, esta indica para que versión de Joomla es aplicable la revisión.

'''Listo para utilizarse''' - El parche se ha probado con éxito y el código puede utilizarse.

'''Cerrado''' - Este estado es para todas las cuestiones que no necesitan realizar ninguna otra acción.

El filtrado es útil en el seguimiento de incidencias. El monitoreo puede ser útil para recibir notificaciones de un problema que se ha actualizado.

Básicamente se inician las pruebas cuando están en el estado de "Pendiente".

=== Preparación de la prueba ===
En primer lugar, el código maestro tiene que recuperadose desde el repositorio GitHub de Joomla. Hay varias maneras para descargar el código master de Joomla pero aquí sólo veremos la opción de descarga.

==== Crear una carpeta====
En primer lugar tenemos que crear una carpeta en el servidor web local o en la cuenta del hosting, accesible mediante el navegador. Crear la carpeta "'bugtesting"' e ir a esta carpeta en el Explorador o Buscador.

==== Descargar Joomla! ====
Vaya a [https://github.com/joomla/joomla-cms localización de Joomla en GitHub] y haga clic en '''Download ZIP'''

[[File:joomla_github-en.png]]

Bajará una copia del código master de Joomla en un archivo ZIP. Descomprima el archivo en una ubicación temporal, verá aparecer una carpeta llamada joomla-cms-staging. Dentro de esta carpeta está el código master de Joomla. Vaya a la carpeta joomla-cms-staging y copie el contenido completo a la carpeta '''bugtesting''' que creó en el paso anterior.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Ahora puede instalar Joomla si está utilizando un servidor web local, navegando a <code><nowiki>http://localhost/bugtesting</nowiki></code>, si se utiliza uno en un servidor web, vaya a la URL adecuada para acceder a su cuenta de alojamiento. Encontrará el proceso de instalación normal de Joomla. En instalar datos de ejemplo, seleccionar: Datos de ejemplo Test English (GB).

¡Esto es importante para que todo el mundo utilice los mismos datos de prueba!

No es necesario que borre la carpeta de instalación, así podrá instalar de nuevo todo, de una manera fácil, si es necesario.

=== Descargar el probador de parches ===
<div class="mw-translate-fuzzy">
Para ayudarle con el proceso de las pruebas de parches, se ha desarrollado una extensión de Joomla Patch Tester. El Patch Tester puede descargarse desde la [https://github.com/joomla-extensions/patchtester/releases página de Patch Tester], después puede instalarla de la misma manera que se instalan todas las extensiones desde el administrador de extensiones de Joomla.
</div>

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

Para utilizar el Patch Tester se requiere una cuenta de GitHub, la razón es que hay un límite estricto en el número de solicitudes anónimas que se pueden hacer a través de Patch Tester. Puede inscribirse para obtener una cuenta de GitHub en [https://github.com/join esta página].

=== Configuración de Patch Tester ===
Los detalles de la cuenta de GitHub se pueden ingresar en los ajustes de Patch Tester. Después de instalar Patch Tester, ve a Componentes -> Joomla! Patch Tester y haz clic en Opciones en la esquina superior derecha. Verás unas casillas donde puedes ingresar tu nombre de usuario y clave de GitHub.

[[File:patchtester_repo-en.png]]

<div class="mw-translate-fuzzy">
En la segunda pestaña llamada Autenticación de GitHub puedes escribir tu nombre de usuario y clave de GitHub, o el token en caso que utilices uno.
</div>

[[File:Joomla PatchTester Github credentials.png|800px]]

Después de ingresar los detalles de tu cuenta, haz clic en Guardar y Cerrar. Una vez de vuelta a Patch Tester, haz clic en Recuperar datos en la esquina superior izquierda.

Ahora está listo para comenzar las pruebas.

Encuentre un problema en el seguimiento de incidencias que desee probar, o utilizar el botón "tener suerte". Compruebe primero si se puede reproducir el problema. Si puede reproducir el problema, entonces puede instalar el parche.

=== Instalación de parches ===
En el Patch Tester encontrará los problemas en los que se está trabajando, bien por título (parcial) o por ID. El título, de un rastreador, siempre se ve así:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

Después de que ha encontrado un parche, haga clic en el botón azul Aplicar parche (Apply Patch). Compruebe si se ha corregido el error y comprobe también si se han añadido nuevos errores.

=== Grabación de resultados de las pruebas ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revertir el parche ===
<div class="mw-translate-fuzzy">
Después de que se ha probado una revisión de seguridad y que ya no es necesaria, se puede remover la instalación de la prueba, de esta manera siempre se está trabajando con un sistema limpio. Vuelva al Patch Tester y haga clic en el botón verde Revertir parche (Revert Patch). Esto quitará el parche y así ya puede empezar a probar el siguiente problema.
</div>

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Translations:Testing Joomla! patches/23/es

2023-10-05T17:47:13Z

Jevsystems:

==== Descargar Joomla! ====

Testing Joomla! patches/es

2023-10-05T17:46:48Z

Jevsystems:

<noinclude><languages /></noinclude>
<div class="mw-translate-fuzzy">
En todo el software hay errores que deben ser corregidos, este es también el caso en un software de código Abierto como Joomla!. El código fuente de Joomla está situado en la internet, por lo que es accesible a todo el mundo. Además hay una posibilidad para el informe de errores. Los errores reportados serán resueltos y eventualmente necesitara de pruebas. Esta página se explica de qué manera puede contribuir al proyecto Joomla con las pruebas de las soluciones propuestas. Usted no necesita tener ningún conocimiento de codificación, usted no necesita una instalación de Joomla para hacer pruebas.
Una Guía de Referencia Rápida para las pruebas está disponible en: [[S:MyLanguage/Testing Joomla! patches QuickReferenceGuide|Guía de Referencia Rápida para Pruebas de parches en Joomla!]]
</div>

=== El código de ensayo en Joomla ===
El código de ensayo de Joomla es el código más reciente en el que se está trabajando. Todas las correcciones de errores y nuevas características se aplican a este código.

El código de ensayo de Joomla lo encontrará en https://github.com/joomla/joomla-cms, este es el código que necesita instalarse. Encontrará la explicación de cómo hacerlo un poco más adelante [[#Preparing to test|Preparación de la prueba]].

=== El gestor de incidencias ===
El gestor de incidencias de Joomla está en: http://issues.joomla.org

[[File:joomla_issue_tracker-en.png|800px]]

Esta lista muestra los errores que están en el tracker en un listado que va del más nuevo al más antiguo, pero puedes cambiar el orden mediante los filtros, en herramientas de búsqueda. En el tracker, todos los errores que tienen un parche, tienen un número de versión junto al título.
* PR-staging: Para Joomla 3.9.x
* PR-4.0-dev: Para Joomla 4.0

Estas etiquetas cambiarán en el futuro a medida que cambien las versiones.

Es importante tener en cuenta el Estado, seguidamente se da una explicación sobre el significado de cada estado:

'''Nuevo''' - Inmediatamente después de que se informa de un problema, recibe este estado. Cuando encuentre un error, cree una descripción de cómo reproducir el error. Las personas que están probando el problema deben de saber cómo probar el parche.

'''Confirmado''' - El equipo de seguimiento ha sido capaz de reproducir el problema. El equipo de codificación va a buscar una solución.

'''Pendiente''' - se ha encontrado una solución al problema. Se ha adjuntado el parche para que pueda probarse. Necesita probarse el problema. Se ha de prestar atención a la etiqueta junto al título, esta indica para que versión de Joomla es aplicable la revisión.

'''Listo para utilizarse''' - El parche se ha probado con éxito y el código puede utilizarse.

'''Cerrado''' - Este estado es para todas las cuestiones que no necesitan realizar ninguna otra acción.

El filtrado es útil en el seguimiento de incidencias. El monitoreo puede ser útil para recibir notificaciones de un problema que se ha actualizado.

Básicamente se inician las pruebas cuando están en el estado de "Pendiente".

=== Preparación de la prueba ===
En primer lugar, el código maestro tiene que recuperadose desde el repositorio GitHub de Joomla. Hay varias maneras para descargar el código master de Joomla pero aquí sólo veremos la opción de descarga.

==== Crear una carpeta====
En primer lugar tenemos que crear una carpeta en el servidor web local o en la cuenta del hosting, accesible mediante el navegador. Crear la carpeta "'bugtesting"' e ir a esta carpeta en el Explorador o Buscador.

<div class="mw-translate-fuzzy">
==== Descargar Joomla ====
</div>
Vaya a [https://github.com/joomla/joomla-cms localización de Joomla en GitHub] y haga clic en '''Download ZIP'''

[[File:joomla_github-en.png]]

Bajará una copia del código master de Joomla en un archivo ZIP. Descomprima el archivo en una ubicación temporal, verá aparecer una carpeta llamada joomla-cms-staging. Dentro de esta carpeta está el código master de Joomla. Vaya a la carpeta joomla-cms-staging y copie el contenido completo a la carpeta '''bugtesting''' que creó en el paso anterior.

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

Ahora puede instalar Joomla si está utilizando un servidor web local, navegando a <code><nowiki>http://localhost/bugtesting</nowiki></code>, si se utiliza uno en un servidor web, vaya a la URL adecuada para acceder a su cuenta de alojamiento. Encontrará el proceso de instalación normal de Joomla. En instalar datos de ejemplo, seleccionar: Datos de ejemplo Test English (GB).

¡Esto es importante para que todo el mundo utilice los mismos datos de prueba!

No es necesario que borre la carpeta de instalación, así podrá instalar de nuevo todo, de una manera fácil, si es necesario.

=== Descargar el probador de parches ===
<div class="mw-translate-fuzzy">
Para ayudarle con el proceso de las pruebas de parches, se ha desarrollado una extensión de Joomla Patch Tester. El Patch Tester puede descargarse desde la [https://github.com/joomla-extensions/patchtester/releases página de Patch Tester], después puede instalarla de la misma manera que se instalan todas las extensiones desde el administrador de extensiones de Joomla.
</div>

The page you are presented with has the Patch Tester 3.0.0 Release Candidate for use on Joomla 3 Sites and the Patch Tester 4.0.0 Release Candidate for use on Joomla 4 sites.
Note that the files to download are hidden in the Assets drop-down which when clicked will review the download file formats and the source code.
Once downloaded it can be installed via the Extension Manager in Joomla.

Para utilizar el Patch Tester se requiere una cuenta de GitHub, la razón es que hay un límite estricto en el número de solicitudes anónimas que se pueden hacer a través de Patch Tester. Puede inscribirse para obtener una cuenta de GitHub en [https://github.com/join esta página].

=== Configuración de Patch Tester ===
Los detalles de la cuenta de GitHub se pueden ingresar en los ajustes de Patch Tester. Después de instalar Patch Tester, ve a Componentes -> Joomla! Patch Tester y haz clic en Opciones en la esquina superior derecha. Verás unas casillas donde puedes ingresar tu nombre de usuario y clave de GitHub.

[[File:patchtester_repo-en.png]]

<div class="mw-translate-fuzzy">
En la segunda pestaña llamada Autenticación de GitHub puedes escribir tu nombre de usuario y clave de GitHub, o el token en caso que utilices uno.
</div>

[[File:Joomla PatchTester Github credentials.png|800px]]

Después de ingresar los detalles de tu cuenta, haz clic en Guardar y Cerrar. Una vez de vuelta a Patch Tester, haz clic en Recuperar datos en la esquina superior izquierda.

Ahora está listo para comenzar las pruebas.

Encuentre un problema en el seguimiento de incidencias que desee probar, o utilizar el botón "tener suerte". Compruebe primero si se puede reproducir el problema. Si puede reproducir el problema, entonces puede instalar el parche.

=== Instalación de parches ===
En el Patch Tester encontrará los problemas en los que se está trabajando, bien por título (parcial) o por ID. El título, de un rastreador, siempre se ve así:

[#4308] - Fixed event dispatching inconsistencies leading to incomplete API

Beside the # is the ID and behind the - sign comes the title.

Después de que ha encontrado un parche, haga clic en el botón azul Aplicar parche (Apply Patch). Compruebe si se ha corregido el error y comprobe también si se han añadido nuevos errores.

=== Grabación de resultados de las pruebas ===
After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.
It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.

[[File:New_testthis_button-en.png|The new Test This button and how to use it]]

=== Revertir el parche ===
<div class="mw-translate-fuzzy">
Después de que se ha probado una revisión de seguridad y que ya no es necesaria, se puede remover la instalación de la prueba, de esta manera siempre se está trabajando con un sistema limpio. Vuelva al Patch Tester y haga clic en el botón verde Revertir parche (Revert Patch). Esto quitará el parche y así ya puede empezar a probar el siguiente problema.
</div>

== Testing patches using Git ==
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.
To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.
The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed
=== Getting the diff ===
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>

To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes
<source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff ===
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>
=== Applying the diff ===
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>

With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff ===
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>

To verify that everything is clean you can run
<source lang="bash">
git status
</source>

You should get the notice:<br />
'''nothing to commit, working directory clean'''

In case the system is not clean you can get a notice like this: <br />
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]

In case you see changed files but you have not made any changes you can cleanup the system with
<source lang="bash">
git reset --hard HEAD
</source>

Now all should be clean

If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.

== Prebuild packages ==
For all people who test Pull Requests for J4: At the bottom of each new PR's is now a link to download an update packages containing the changes from this specific PR.
Maybe you have to expand the details for the tests first. For this click on <tt>Show all checks</tt>.

[[File:PrebuildPackages1-en.png||Maybe you have to expand the details for the tests first.]]
Then you see the link to the download. Click on <tt>Details</tt>.

[[File:PrebuildPackages2-en.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and update packages.

[[File:PrebuildPackages3-en.png||Then you see the link to download.]]
This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.
Unzip the file in a temporary location, a folder named <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> will appear.
For Version <tt>4.0.0-beta1-dev</tt> and PR-number <tt>28462</tt> this will be for example <tt>Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package</tt>.
Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder <tt>bugtesting</tt> and go to this folder via Explorer or Finder.
Go into the <tt>Joomla_[Version]+[Number of Path]-Development-Full_Package</tt> folder and copy the complete contents to the folder <tt>bugtesting</tt> that you created in the previous step.

Now you can install Joomla by navigating to <tt>http://localhost/bugtesting</tt> if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4-en.png||Set up your sytem.]]
For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos==
===How to test patch for Joomla 4 ===
{{#widget:YouTube|id=22RXppJjXf8}}

===How to test patch for Joomla 3 ===
*Part 1: Introduction
{{#widget:YouTube|id=zmnWkMisdJk}}

*Part 2: Neard Web Server setup
{{#widget:YouTube|id=Tqj-BAmPGLA}}

*Part 3: Sample issue testing.
{{#widget:YouTube|id=s881RLaFO8U}}

===How to test Prebuild packages for Joomla ===
Joomla has instigated a new method of testing pr's that will greatly benefit those on shared hosting. Or those who simply want a simple pr testing method.
{{#widget:YouTube|id=22RXppJjXf8}}

== Link==
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>