Test Plan
Deltares Systems Software commitment to quality control and quality assurance has leaded them to develop a formal and extensive procedure to verify the correct working of all of their geotechnical engineering tools, including a test plan.
The Test plan document can be as varied as the products and organizations to which they apply.
This section describes how these tests will take place at three different levels:
- 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:
Number of unit tests
Code coverage of the unit tests (not done)
Specify if all unit tests succeed or not
- 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:
- Number of integration tests (= Benchmarks)
- Code coverage of the unit tests (not done)
- Specify if all integration tests succeed or not
...
3. 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:
- Alle main functions must provide the correct answers (detailed results of these tests can be found in the Test Report) to confirm its performance according to the functional design.
- All possible errors must be handled and reported properly.
Based on the formulae in the Functional Design for D-Flow Slide benchmarks were created to test the kernel and the User Interface.
Test Report
The following chapters describe the tests in detail. If all tests are run with a satisfying result, the kernel is said to be good
The Userinterface has been tested manually by students using the Checklist for the program, based on the usermanual with technical requirements.
Number of Unit tests
- Deltares.FlowSlide.Data.Tests : 291 tests inclusive benchmarks (test the calculation)
- Deltares.FlowSlide.Forms.Tests : 40 tests (test the UI of D-Flow Slide)
Benchmarks - Integration tests
These benchmark (integration test, 29) . An extensive range of benchmark checks have been developed to check the correct functioning of each tool. During product development these checks are run on a regular basis to verify the improved product.
These benchmark 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:
...
The spreadsheets used for benchmarks in group 3 can be downloaded here.
Overview of the benchmarks
Legend:
= Results of D-Flow Slide and results of the Benchmark are identical.
= Results of D-Flow Slide and results of the Benchmark differ.
...