Joomla! Documentation™

This article is designed to help Joomla! Bug Squad members as they test Open issues and Pending issues.

Testing Open Issues

The "Open" status indicates that no JBS member has evaluated this issue. So the goal is to learn enough about the issue to be able to change the status to one of the following: Unable to Confirm, Known Issue, Duplicate Report, Not Joomla! Core, Confirmed, or Information Required. See Reporting issues for details about these statuses.

Here is a checklist for testing Open issues:

• Did you carefully read the whole description and any other comments?
• Is there enough information provided? If not, add a comment and change to Information Required.
• Did you search the tracker to see if this issue has already been reported? If so, add a comment and change to Duplicate Report.
• Does the issue relate to a Joomla! core program? If not, change status to Not Joomla! Core.
• Is the issue a known issue or limitation? If so, change status to Known Issue.
• Is the issue an enhancement request? If so, change status to Not a Bug.
• Before testing, did you update your local SVN repository to get the latest SVN Joomla! version?
• If you couldn't duplicate the problem with the latest SVN version, did you test using the latest production version?
• If you changed the issue to Confirmed, did you make sure there is a detailed test plan in the comments to allow someone who is not familiar with the issue to understand and test the issue?

Testing Pending Issues

A Pending issue is one that (a) has been confirmed, (b) has a detailed test plan, and (c) has a proposed patch to be tested. Here is a checklist for testing Pending issues:

• Is there a test plan for the issue? If not, post a comment and change status to Information Required.
• Before testing, did you update your local SVN repository to get the latest SVN Joomla! version?
• Did you test the issue before applying the patch to make sure you can duplicate the problem?
• Did you test the issue after applying the patch to make sure the problem is fixed?
• Are there any other test cases that should be considered? Examples might include:
  • template override files (especially beez template)
  • testing with SEF or mod_rewrite enabled and disabled
  • language file issues (test with Debug Language set to Yes).
  • PHP warnings (test with Error Reporting set to Maximum).
• If your test is successful and you are the first tester, indicate in your comment that a second test is needed. If you are the second tester, change the status to Ready to Commit.