- First, do the things you normally do and see if you spot any problems.
- Look at all of the front end views and record any problems
- Look at all the back end views and report any problems
- See more ideas below
What to look for
- Any error messages that say things like Fatal Error or Strict or similar things that indicate that something is not working correctly.
- Untranslated strings. You will know these because they look like this: ?STRING_HERE?
- Problems of rendering–items not aligned correctly, missing or wrong images, pages that just don’t look right.
- Unexpected behavior–anything that is working differently than it did in 2.5.
If you find a problem please report it to the CMS Issue Tracker. You will need to register for a github.com account if you don’t have one.
More Testing Ideas
- Pick one module or view and test all of the parameters.
- Install an extension and see if anything breaks (report to the developer unless you are positive it is a core bug).
- Turn on caching with different options
- Try different session options
- Install a language and test all the layouts.
- Try different environments (like different servers which may have different version of PHP) or try you have IIS with MySQLi or SqlSrv. With millions of users Joomla needs to be ready for unusual environments.
- Try with SEF URLS on or off and also with Apache rewrite on or off (if you are on Apache).
- Try different combinations of browsers (Chrome, IE, FireFox, Opera to start) and operating systems (Mac, Windows, Linux).
- Yes grammar and spelling errors are bugs too — just keep in mind that we use British spelling.
- Visit the Feature Tracker and test a new feature.
You can also help Joomla by testing bug fixes and new features. A useful tool is the patchtester component which helps to simplify and automate the process. Report your feedback on the CMS Issue Tracker. If you enjoy helping Joomla this way, you may want to join the Joomla Bug Squad.