Having your customers' trust is vital for every company. Against this backdrop, managers set up a quality assurance process that consists of strengthening the customer's trust and the company's credibility, and to allow the latter to compete more effectively against its competitors.
This quality assurance process mainly concerns the organization and the means deployed by the company to guarantee quality. The goal of this assurance is to achieve and maintain the desired quality. Thus, NeoDoc adopted a quality assurance process to guarantee the quality of its products to its customers.
Camille Bégnis, founder of NeoDoc, talks about the number "“2726”", which illustrates this quality process well: it corresponds to the number of automatic tests that are carried out to guarantee the quality of the Calenco software.
In this interview, he explains the importance of the tests carried out to guarantee the quality of the Calenco software, dedicated to writing, translating, publishing and distribution of companies' strategic documents.
This figure represents the number of automatic tests that are carried out on Calenco to evaluate all functionalities. These tests, carried out with each new version of Calenco, encompass all security and functionality aspects of the software platform.
We work with many large accounts (EDF, SNCF, General Electric: Bouygues Construction…), and we must provide them with this quality assurance. It benefits all of our clients, whatever their size.
Yes, they represent the quality of software functionality.
They are automatic scripts that reproduce a platform use scenario and verify that each of the user functionalities and security constraints are in conformance with the initial specifications.
The tests are carried out directly in the API (Application Programming Interface). What's more, exhaustive manual tests are carried out on the graphic interface.
This figure represents the number of tests carried out to ensure that no regression occurs in new versions of Calenco. It is continually increasing, to take new functionalities into account. An update cannot be carried out unless the result is 100% positive. During testing, these results are not always satisfactory. Therefore, before the update can be made, we must carry out corrective actions on the code until we attain 100% success.
They are essential. Without them, we would have to do all of the tests manually, which would take an enormous amount of time and carry the ever-present risk of human error.
They are carried out on several browsers and several operating systems, each time there is a new functionality.