Software testing in the railway sector poses considerable challenges for all involved due to the ever growing and more complex systems. This begins with the definition of a set of test cases that provide evidence of the functional and non-functional requirements. Furthermore, the test methods required by the applicable standards must be used (cf. DIN EN 50128) and tes cases must be defined and implemented. The challenge during implementation is to recognise as early and as quickly as possible which parts of the test case code can be reused in order to transfer these parts to a test library. However, it can be seen again and again that testers in many projects tend to duplicate their test case code rather than convert any parts of it into central library functions due to project deadlines. Any errors in the definition of the test case suites or the avoidance of any central test functions steadily increase the expenditure on testing process units such as verification, validation and assessment, as a lot of time has to be invested in reviews and impact analyses. Every unnecessary test case, which brings no further knowledge, and every duplicated code, which has to be subjected to a review every time, means the unnecessary outlay of time and resources. This has prompted the authors to investigate the question as to whether there are alternative concepts or procedural models available to increase the effectiveness of test case implementation and the subsequent reviews.
Benjamin Mensing, Florian Haux and Lars Schnieder investigated the question as to whether there are alternative concepts or procedural models available to increase the effectiveness of test case implementation and the subsequent reviews. Read their results in the current issue of the trade magazine "Signal + Draht" (5/2020). We gladly provide you with the article free of charge. Please send us an e-mail with the title of the article to pr(at)ese.de.