it's all about software testing...it's all about software testing. 2 situation:...

V1.0 | 2018-11-06

Concepts for Unit and Functional System Tests

It's All About Software Testing

2

Situation: Perspective of Unit Testing and Functional System Testing

3

Goal: Joined Perspective of Testing

Introduction

4

Test Concepts

Early test of

components,

independent of

availability of

other components

Reuse in the test

design

Flexibility in the

chosen test design

method

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

5

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Flexibility in the

chosen test design

method

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

6

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Flexibility in the

chosen test design

method

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

7

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

8

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

9

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

10

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

11

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

12

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

13

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

14

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

15

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

16

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Traceability and

Continuous

Integration

17

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Measure code

coverage both

with unit and

system tests

Traceability and

Continuous

Integration

18

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Measure code

coverage both

with unit and

system tests

Traceability and

Continuous

Integration

19

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Measure code

coverage both

with unit and

system tests

Traceability and

Continuous

Integration

Connection to test

management tools

and Jenkins,

changed-based

testing

20

Test Concepts

Early test of

components,

independent of

availability of

other components

Usage of models

Reuse in the test

design

Separation of test

logic,

implementation

and test data

Flexibility in the

chosen test design

method

Integration of

different test

notations in one

tool (graphical,

tabular, coding)

Consideration of

both DUT and test

variants

Variant handling

for test structure,

test logic and

parameters

Adequate test

coverage

Design features

for definition of

relevant test case

data and

generation of test

cases

Analysis and

reporting during

and after test run

Analysis windows,

e.g. for

visualization of

value charts

Code coverage to

meet standards as

ISO26262,

IEC62304,

DO-178B

Measure code

coverage both

with unit and

system tests

Traceability and

Continuous

Integration

Connection to test

management tools

and Jenkins,

changed-based

testing

21

Conclusion

The requirements and challenges on test environments of HIL system tests, SW system tests, integration tests and unit tests are widely the same

Corresponding test concepts are applicable to all kind of tests

Vector strategy: provide a comprehensive test solution for all kind of tests based on well established tools

Combine the strength of vTESTstudio and CANoe for system tests with the strength of VectorCAST for code based tests

22 © 2018. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 | 2018-11-06

Author:Katranski, UteVector Germany

For more information about Vectorand our products please visit

www.vector.com