|
|
| (6 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{Plugins development}} | | {{Template:Migrated|newDocId=/general/community/plugincontribution/guardians/qaprechecks}} |
| | |
| Plugin QA prechecks are tests of the basic functionality of plugins submitted for approval in the Moodle Plugins directory. Together with [[Plugin code prechecks|code prechecks]], they are part of the plugin [[Plugin contribution|approval process]].
| |
| | |
| These QA prechecks can be performed by any Moodle community member. They allow the developers to focus fully on the code review and so they significantly contribute to the fluent flow of the plugin approval reviews.
| |
| | |
| The main areas covered by the plugin QA include:
| |
| | |
| * Checking the plugin description and some other plugin's meta-data.
| |
| * Installing the plugin to see that it does not break or otherwise negatively affect the site functionality (anti-regression test). This also checks that all eventual dependencies are already available in the plugins directory.
| |
| * If possible (e.g. if no complex integration with an external system is needed), test the actual functionality of the plugin to see it works as described (feature test).
| |
| | |
| See [[Plugin contribution checklist#Meta-data|Meta-data]] and [[Plugin contribution checklist#Usability|Usability]] sections at the plugin contribution checklist page for details.
| |
| | |
| === QA environment setup === | |
| | |
| * Have developer debugging enabled with debugging messages displayed.
| |
| * Report all PHP notices, warnings and errors spotted durign the plugin installation and usage.
| |
| * It is recommended to test on a site running on PostgreSQL database engine to catch potential MySQL-specific SQL statements in the code.
| |
| * Have the <tt>$CFG->prefix</tt> set to a non-default value, such as "m_" or "mqa_". This allows to catch cases when the default "mdl_" prefix is hard-coded in PHP.
| |
| | |
| === Process ===
| |
| | |
| # Pick a plugin from the list of plugins awaiting approval.
| |
| # Perform the QA prechecks.
| |
| # Comment on the relevant plugin approval issue (CONTRIB-xxx as mentioned at the plugin page comments area, or at its development tab) and report your findings.
| |
