Quality Assurance

 

One of the reasons 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 get 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."

 



Sample Windows Test

Use Cases

Our use case testing starts at the most basic level--populating an empty database--and moves all the way up through the most advanced functionality available in xTuple ERP. If you're interested in seeing more details on our use cases, click on any of the following links. This information, maintained in Google Docs spreadsheets, is continuously updated in real time.



Sample Mac Test

Automated Testing

Our automated test scripts are written using Squish, a tool designed specifically for testing cross-platform applications (like xTuple ERP) which are built using Qt. The beauty of an approach like this is we can write one test script, then run it against all our supported clients and all the xTuple ERP Editions. The videos to the left are samples from our growing set of automated test suites.

Anyone who has a licensed copy of Squish can run our test scripts for themselves. We maintain the scripts in a repository on Github.

Interested in helping out? Familiar with writing automated test scripts? Feel free to drop us a line...

 

 

 

Process Overview

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

At present, the majority of our tests are performed manually--against the Manufacturing Edition on both Windows and Mac. However, we are working to automate as many of our use cases as possible. xTuple is committed to automated testing--and to the fully cross-platform, cross-edition coverage it affords.

Community feedback is received continuously, from all over the world. Most often, new users identify problems they've encountered in one of our public forums, where an initial discovery phase helps to validate a problem. Formal bug reports should be posted in our issue tracker, for further processing. To post bugs in the issue tracker, users must have Full Access privileges.

 

 

 

 

 

 

mead