Services

Embedded Systems Testing

Pentalog High Tech has adopted a project approach based on the V-cycle for testing embedded systems. Tests are indeed crucial, considering the strong constraints related to these systems. In order to meet these requirements, Pentalog High Tech accompanies the classical V-cycle model with the development of an adapted test cycle which enables the system to be operated securely.

Product Testing

Software Testing

• Phase 1 - Start

  Test planning consists in the verification of the test mission by defining objectives. The purpose is to compare the real progress in relation to planning and to report the status, including any modifications.

• Phase 2 - Analysis and design

  The general objectives of the tests are transformed into test conditions and test cases. The main tasks are the creation of the database, the identification of test conditions, the priority for each test case and, finally, the identification of the necessary tests corresponding to the test conditions and cases.

• Phase 3 - Implementation and execution

  This phase involves the implementation of test cases and execution of test scripts such as the development of test procedures, the creation of test data and the test sequence, the verification of the test environment, the execution of the test procedures either manually, or by using tools, data verification, the identification of bugs and the re-execution of the test cases.

• Phase 4 - Data validation and reporting

  This phase allows the comparison with the objectives defined for each test case, a verification of the log files.

• Phase 5 - End of test

  The test ending activities gather the data of the activities carried out during the tests, the software program used, the facts and the results.

  • Verifying that the anomalies found during the tests are solved, preparing the documentation for delivery
  • Preparing the deliverables
  • Transferring the tested software into the maintenance phase
  • Analyzing the experience gathered so that it may be used in the future and improving the "maturity" of tests.

• Integration test: test verifying proper performance during the preparation of procedures and modules
• Validation test (system test): adequacy in regard to the specifications
• Non-regression test: verifying that the corrections or the code evolutions have not generated any new anomalies.