Qualification of the release of a version of our software entails a strict, comprehensive validation process.
It allows us to guarantee the quality of results throughout software development.
Validation is also present throughout the development of the version. Work done is tested during development.
During the creation of a new version, a very strict, precise specification is drawn up and then discussed with the different services involved: R&D, Quality, Applications, Methodology, and Documentation.
Subsequently, different work packages corresponding to these specifications are developed separately, and validated autonomously, before being integrated into the development version and included in the broader validation process.
In the example of Flux, the validation process is applied to all programmes: Flux 2D, Flux 3D, Skew, Supervisor, Materials Manager, Licence Manager, different couplings (GOT-It, MATLAB / Simulink®, Portunus…), etc.
In general terms, all couplings with third-party CAD solutions are systematically checked during development.
The validation process is applied rigorously to the different operating systems and calculation platforms with current validity.
The validation process comprises three sub-groups and in the case of Flux:
Test of different Flux modules excluding supervisor
These tests are automated by Python Scripts
Windows 32 : 1262 test cases
Windows 64 : 1263 test cases
Linux 64 : 1196 test cases
IHM test of different Flux modules
Manual tests (tutorials + IHM procedure for new functionalities)
Flux supervisor test
System installation test
System protection test
The test case database has, through the different versions, allowed us to capitalise on tests on all the different functionalities of our software to ensure non-regression. These validations are done both at the level of project compatibility and precision of results obtained on the operating systems and calculation platforms used.
Further tests are systematically built for new functionalities to enrich our database.