Page History

...

1. Code level - unit test: Program code must be tested alongside the code. Such a test checks if the code does what it is supposed to do with a little test. The tests on code level are the unit tests. For each relevant function, a unit test is defined within the C# solution. A relevant function is a function that actually performs part of the calculation, validation or I/O of the core. Properties and purely administrational functions do not have unit tests.

   These tests are considered to be ok when the unit tests pass and when the code coverage of those tests is more than 75%. For these tests the following information must be provided in the Test Report:

    

   1. Number of unit tests

   2. Code coverage of the unit tests

   3. Specify if all unit tests succeed or not 
      
      

2. Functional level - integration test: The tests on functional level are the integration tests. These types of tests combine multiple functions in D-Flow Slide to prove that high level functionality works. For this, a unit test is defined within the C# solution for each method with high level functionality. These tests are considered to be ok when the unit tests pass. The following information must be provided in the Test Report:
3. Number of integration tests (= Benchmarks)
4. Code coverage of the unit tests
5. Specify if all integration tests succeed or not
   
   
6. Application level (System tests) :  The tests on this level are to provide proof of the fact that the D-Flow Slide meets its acceptation criteria. The criteria are:

...

These benchmark (integration test, 29) checks are provided in the following sections, to allow the users to overview the checking procedure and verify for themselves the correct functioning of D-FLOW SLIDE.
The benchmarks for Deltares Systems are subdivided into five separate groups as described below:

...