ClassicPress Documentation

Testing ClassicPress

ClassicPress is focused on quality.Link to this section

Our Quality Assurance (QA) team focuses on testing and software quality, as well as making sure any bugs get in front of the right people so they can be fixed.

Continuous QA is crucially important in software development because it helps to ensure that any change or update will keep the quality of the software and avoid any new defects or bugs.  Software bugs and defects can have a huge negative impact on the businesses/people that use the software.

How can I help the QA Team?Link to this section

We will need all the help we can get to cover all the necessary testing scenarios.

We’ve released ClassicPress 1.0.0-beta1 (the first official beta release) and we need help testing new installs of ClassicPress using this version.

We’ve also released the migration plugin that will convert a WordPress installation into a ClassicPress installation, and we need help testing that too.

To install ClassicPress using either of these methods, see the Installing ClassicPress page.

For a suggested list of testing scenarios, see the Testing Scenarios page.

To find out more, join our Slack group and introduce yourself in the #testing channel, or make a post on our support forum.

Testing process and requirementsLink to this section

You will need a computer to perform the testing, and of course some free time. Even a few minutes to perform a fresh install or a migration from WordPress to ClassicPress can help.

You should test in new installs or existing site installs that aren’t in production and aren’t important in case something goes wrong.  And of course, always make a backup of your site files and database first!

Reporting bugsLink to this section

Any bugs that are found can be reported on the GitHub project pages.

You can report bugs in ClassicPress itself on the ClassicPress GitHub repository.

You can report bugs related to the ClassicPress migration plugin on the GitHub repository for the plugin.

We are happy to help you through the process of reporting a bug as well, just send us a note on Slack or email.

Manual and automated testingLink to this section

There are two main types of software testing that can be done. One is manual testing done by real people and the other is automated testing that is performed by computers.

The idea is to have always a mix of both kinds of testing to increase and maintain ClassicPress software quality.

ClassicPress core has an extensive PHP and JavaScript automated test suite, which is based on the WordPress automated test suite.  This test suite runs against the ClassicPress code every time any change is made, and the tests are required to pass before the change can be merged.

New code or logic introduced into ClassicPress or its plugins should also have automated tests.

For more information see the WordPress automated testing handbook – most of the same information applies to ClassicPress.