Evaluation Environment for AUTOSAR-Autocode in Motor Control ...

5.2 Components of the Environment
which options are used for the test. If the test is performed, the concrete parameter
for the used RTE generator is substituted. An option has a description that explains
the purpose of the option.
5.2.3 RTE Library
Similar to the options, the libraries are treated. An RTE generator provides normally
the library which is delivered with it. This library is called “Original” in the environment.
However, there can be other libraries, which are customized to take care about
special needs of e.g. MEDC17. This library is called “Mx17Erco” in the environment.
These two libraries are the only, which are currently used. The test template specifies
a library to be used and a generator can provide an implementation for this library,
or not.
5.2.4 Resource
Resources are the basis of the tests. Typically they consist of AUTOSAR XML and
source files. The XML files are normally fed into the generator and the source files
implements the SWCs, which are configured in the XML files. The resources are
handled separately to provide a better access with external tools and reusability for
multiple test templates.
5.2.5 Test Type
The test types specify how a test should be performed and how the result is obtained.
A test type consists of a name, which identifies the type. The description is a short
characterization of what the test type does. The Perl file implements the concrete
behavior of the type and it is explained in section 6.4. It is used to perform the test
type automatically.
In section 5.1 it is described, that for compiling the source code the RTE generator
has to accept the configuration and create the RTE. Thus, compiling of the source
code depends on whether the RTE generator accepts or rejects the configuration.
Furthermore, for a test it could be enough to know, if the generator accepts or rejects
a configuration. So there can be some test types like “accept”, “reject”, “compile”
imagined. To keep the effort down, the test for compiling a generated RTE can revert
to the test “accept”, which obviously has to be finished successfully before. This leads
to the dependencies between test types.
In section 5.1 it is also described, that for the operating system configuration additional
OIL files and for compiling additional source files are needed. So a test type
also has to provide some files that are needed for performing this type.
The types, which are used in the environment, are shown in figure 5.3 together with
their dependencies. The test types in the blue boxes can be performed automatically
without an interaction of the user. The result can be obtained from return values of
the executed programs. The blue boxes show the tests, which are performed by the
39