Testing is a crucial part of plugin development to ensure high quality, bug-free, and compatibility with other themes, plugins, and older WordPress and PHP releases.
In case you want to test the beta and release candidate versions, here are a few points to get you going.
Any bugs or other issues are reported to email@example.com. Please also report successful testing, as this will give the plugin author valuable information for how stable the plugin is running.
- Put the rml_readmore shortcodes in one of your posts or pages, and check text will be hidden when not logged in.
- Test you can log in using the read more form.
- Test register a new user using the registration form.
- Add profile and password shortcode to other pages, and test you can update the profile and change passwords.
- Log out, and test you can request a password reset link by e-mail (by using the page with the password shortcode)
- Test all links in the forms are redirecting to correct pages. (The registration link, password link, etc.)
Repeat all the basic tests by using different
- Web browsers like Chrome, Firefox, Safari, Edge, and possible others.
- Run the tests on different platforms like PC, pads, various mobile devices.
You should run all these tests with the theme you want to use and with all plugins activated. This can uncover conflicts with other plugins.
- Enable debug logging in plugin’s advanced settings. During testing, no errors should be reported in log. (These are messages starting with “ERROR”. “WARNING” messages may be acceptable and indicate invalid settings.) Rerun some of the basic tests.
- Try to enter invalid data, like invalid formatted e-mail, or try not to enter any data when required. Observe appropriate error message is given and the input field gets a red border around.
- Language test. If you are expecting sign-ups of non-English users and expecting these to use international characters normally not used by the English language, test registration, and profile change with such characters.
- Try to click the registration links a second time. If not logged in, hidden content must not show, and the user will be asked to log in again or register a new user.
- If you are really into the testing, you can also try to alter some of the settings and check plugin change accordingly.
Your contribution is appreciated
Testing takes a lot of time and it can account for as much as 50% of the development work. WordPress plugins may in particular need extra attention due to the requirement for being compatible with lots of themes and other plugins, combined with older WordPress and PHP releases.
As the plugin developer’s time is very limited, such contributions are highly appreciated. This will also help speed up the development work and shorten the release cycle.