Skip to content

Double process testing

JVerbruggen edited this page Jan 11, 2021 · 2 revisions

Software integrity is of critical importance for applications in the railway industry. Engineers often use double processes to meet this integrity level. This means that functionality is tested by executing a separate tool that solves the same problems, then evaluate the outcomes. The difference between both tools is that the second tool has to be developed independently from the original tool by different developers. If the outcomes of both tools are equal, the tested functionality of the first tool is validated.

A quick way to put this double process to the test for this application is to have an independent developer create a translation algorithm in a language such as Python since this can be implemented more quickly. Extensions such as the pathfinder and the net-entity locator can also be recreated and validated like this. Outcomes for these algorithms should be equal across tools.

Clone this wiki locally