What is xTuple's quality assurance (QA) practice?

For every release, xTuple is submitted to a rigorous QA process, using a combination of automated test scripts, more detailed manual use cases and feedback from community beta testers.

"Given enough eyeballs, all bugs are shallow."

One reason xTuple ERP is such a reliable business solution is that, for every release, we submit the application to a rigorous Quality Assurance (QA) process. Using a combination of automated test scripts, more detailed manual use cases, and feedback from community beta testers, the QA team provides our developers with valuable feedback throughout the software release cycle. This page is designed to familiarize people with our testing methods — and, hopefully, to inspire even more community members to be involved with testing and providing feedback on our products. Community involvement is critical to the continued success and improvement of xTuple ERP. As Eric Raymond wrote in The Cathedral and the Bazaar years ago, "Given enough eyeballs, all bugs are shallow."

Process Overview

The QA team follows a standard schedule during the software release cycle to ensure consistent results are achieved. As a general rule, automated tests are executed first, followed by manual testing of the remaining use cases.

Use Cases

Our use case testing starts at the most basic level — populating an empty database — and moves all the way through the most advanced functionality available in xTuple ERP. The following categories indicate, in part, the scope of our automated testing:

  • Process Flows
  • Modules
  • Advanced Features
  • Privilege Testing
  • Migration Testing
  • Batch Manager

Automated Testing

Our automated test scripts are written using Squish, a tool designed specifically for testing cross-platform applications (such as xTuple ERP) which are built using Qt. With this approach, we can write one test script, then run it against all of our supported clients.

Anyone who has a licensed copy of Squish may run our test scripts themselves. We maintain the scripts in a GitHub repository.

Interested in helping? Familiar with writing automated test scripts? Contact us.