Many customers have issues with understanding the various testing methods in the ISO 26262 standard. To say it in a diplomatic manner, ISO 26262 parts 4, 5, and 6 mention e.g. equivalence classes and boundary values as methods for deriving test cases but they do not explain much about these methods in detail. The ISO 26262 standard was derived from IEC 61508, the mother of all safety standards, and in fact the methodologies of these two standards still overlap at some of the topics. More helpful inputs about the equivalence classes, boundary values or error guessing methods can be found in the IEC 61508.<\/p>\r\n\r\n\r\n\r\n
According to IEC 61508-7, boundary values analysis is used e.g. to detect software errors at parameter limits or boundaries. The derived test cases are covering boundaries and extreme classes. Those input classes are previously divided using the generation of equivalence classes method.<\/p>\r\n\r\n\r\n\r\n
The test is checking the boundaries in the input domain. The use of the value zero, in a direct as well as in an indirect translation, is often error-prone and shall receive special attention to the following:<\/p>\r\n\r\n\r\n\r\n
- \r\n
- zero divisor;<\/li>\r\n\r\n\r\n\r\n
- blank ASCII characters;<\/li>\r\n\r\n\r\n\r\n
- empty stack or list element.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
Ultimately, a test should be defined that causes the outputs to exceed the specification boundary values. In other words, the test cases shall force the output to its limited values, through the boundaries at the input with direct impact on the output range, or through evaluation which boundary values at input are needed to cause boundaries at the output.<\/p>\r\n\r\n\r\n\r\n
Boundary values examples at hardware design<\/h3>\r\n\r\n\r\n\r\n
As part of functional testing, Boundary Value Analysis is based on testing the boundary values of valid and invalid partitions.<\/p>\r\n\r\n\r\n\r\n
E.g. Temperature sensor with valid range of -20\u00b0C to 125\u00b0C shall be tested:
Calculation of boundary values for:<\/p>\r\n\r\n\r\n\r\n- \r\n
- Minimal value = -20\u00b0C<\/li>\r\n\r\n\r\n\r\n
- Just above the minimum = -19\u00b0C<\/li>\r\n\r\n\r\n\r\n
- Nominal value = 65\u00b0C<\/li>\r\n\r\n\r\n\r\n
- Just below Max value = 124\u00b0C<\/li>\r\n\r\n\r\n\r\n
- Max value = 125\u00b0<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n\u00a0<\/div>\r\n\r\n\r\n\r\n
E.g. for the n variable to be checked, maximum of 4n + 1 test case will be required. Therefore, for n = 1, the maximum test cases are:
4 \u00d7 1 + 1 = 5
Invalid boundary values to be tested at min-1 (-21\u00b0C) & max-1(126\u00b0C)<\/p>\r\n\r\n\r\n\r\nAt an MCU, test blocks related to safety mechanisms e.g. temperature sensors & ADC can be tested using fault injection methods. Test cases can be derived using methods like analysis boundary values.<\/p>\r\n\r\n\r\n
\r\n![\"\"](\"https:\/\/lorit-consultancy.com\/wp-content\/uploads\/2024\/06\/Img.1-MCU.png\")
<\/figure>\r\n<\/div>\r\n\r\n\r\nThe test cases on hardware detailed design level shall show the compliance with requirements and cover where applicable the test results for the integration level.<\/p>\r\n\r\n\r\n\r\n
Error Guessing<\/h2>\r\n\r\n\r\n\r\n
Error guessing is a testing technique where experienced testers use their intuition and knowledge about the system or similar designs to evaluate some uncategorized test cases and use them for the verification. The aim is to predict areas where defects are likely to occur. This technique relies on tester\u2019s knowledge of common or typical failures that might arise in similar systems which leads to structured test cases.<\/p>\r\n\r\n\r\n\r\n
\u201cError guessing tests\u201d can be based on data collected through a lessons-learned process or expert judgment or both. It can be supported e.g. by a FMEA.<\/p>\r\n\r\n\r\n
\r\n![\"\"](\"https:\/\/lorit-consultancy.com\/wp-content\/uploads\/2024\/06\/Error_guessing_expert-1024x574.jpg\")
<\/figure>\r\n<\/div>\r\n\r\n\r\nApplication of Error Guessing<\/h3>\r\n\r\n\r\n\r\n
Tester tries identifying common failures that have occurred in the past, such as boundary values issues, and then defines specific test cases to target these potential issues. Analyzing defects found in similar projects can help predicting similar issues in the current system aka lessons learned. Based on the experience and knowledge, the testers can explore the design of the system using error guessing methods to test various inputs and interactions that might lead to errors.<\/p>\r\n\r\n\r\n\r\n
The error guessing can lead to further methods of defining and application of test cases:<\/p>\r\n\r\n\r\n\r\n
- \r\n
- Boundary values: entering values just inside and just outside the valid range<\/li>\r\n\r\n\r\n\r\n
- Fault injection: injection of invalid inputs with specific values<\/li>\r\n\r\n\r\n\r\n
- Resource usage evaluation and testing the system\u2019s behavior when resources are exhausted<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
Error guessing method can help to identify potential errors at specific items of the system very quickly, using the tester\u2019s knowledge and experience. It is a very flexible method that allows to adapt and respond to findings in short time. It is a valuable technique for identifying defects that might not be covered by other testing methods, leveraging the unique insights and experience of skilled testers to enhance the overall testing process.<\/p>\r\n\r\n\r\n<\/div><\/div><\/div>
![\"\"](\"https:\/\/lorit-consultancy.com\/wp-content\/uploads\/2021\/01\/dijaz-maric-640x640.webp\")
<\/picture>