Software unit test
Erik Andersson, Simon Börjeson · Chalmers Publication Library (Chalmers University of Technology) · 2014
The upcoming version of the ISO standard 26262 requires all software to be unit tested by the developers.The work is about improving Volvos current risk prioritization method for software at a unit level.As a result, Volvo has a new method to use when they perform risk analysis on units from models in Simulink.The analysis consists of two major parts, the likelihood and consequence.Both parts are dependent on a number of subcategories which is visualized as a matrix.After the risk analysis, the unit receives a unit risk prioritization score, which indicates how important it is to perform a unit test for this part of the software.The score also determines how large coverage the test should have while testing.Another part of the work was to find a way to split models into smaller parts for unit testing.When the software engineers split down the models to an understandable size of a unit, the group found the cyclomatic complexity of the units were at a similar value.This could be measured with MATLAB Verification and Validation toolbox.The work does not consider what kind of unit test that should be preferred to different parts of the software.