At CourseSales.com we take testing very seriously. The smarter we test the less risk there is to those using CourseSales.com. We cannot guarantee that everything will go according to plan. While we will test as much as we can we encourage you to do your own testing and are happy to provide guidance and assistance in doing so. The following is recommended for each level of use of CourseSales.com:

Fundamental functions

• do not integrate pages with their website

• do not use any plugins

• do not use the API

• have standard pricing

Standard functions

• use plugins

• integrate existing forms in their standard state (without customised CSS or JS files)

• use portals and plugins

• report using AVETMISS

Sensitive functions

• use plugins, with customised versions of the software, or non-tested versions

• integrate with the API outside of existing plugins or use other means to re-code existing delivery of pages

• have customised JS files or CSS files to change look and feel of portal or form pages.

We encourage you to use our test environment if you use any sensitive functions, and optionally if you have any medium safe functions. Here are some tips:

• Your test environment when set up will be at the URL: https://<shortname>.test.coursesales.com (note that when using moodle or other plugins you will need to use http NOT https)

• Emails are not sent to anyone other than that designated by you (contact us to send us your preferred ‘test’ email recipient)

• The test environment contains data that will be over-written after each upgrade, we load up the production database so to replicate as closely as possible the actual production environment. That means that logins and passwords will also be the same in test at the point the data is migrated.

Levels of Testing

The recommendations are cumulative.

See Testing using Selenium IDE, tips and hints

Basic

• Make a booking

• Check emails sent, received and any links in them

• Take a document through each process step (on each process path)

• If you have any discount codes or catalog items purchase then and check these are maintained

• Check any PDFs, and variables are replaced

Medium

• Do an AVETMISS report

• Check that adding a document includes the necessary document topics

• Check any pricing discounting, automated or not still work as expected

• Check integrate with website, process a booking from the website and from the admin portal

• Check access to the student portal and trainer portal work as expected

• Confirm Moodle course creation, access and completion work as expected

Thorough

• Add a new course master, new course date, with new catalog items and pricing rules

• Add documents, cancel documents

• Confirm all third party applications still interact as expected

• Target any errors or issues previously encountered to confirm they do not re-occur

• Confirm that any customized CSS or JS files still perform as expected