Component Testing for C overview

Component Testing for C

The Component Testing for C feature of OneTest Embedded provides a unique, fully automated, and proven solution for applications written in C, dramatically increasing test productivity.

Component Testing for C supports ANSI C89 and C99.

How Component Testing for C Works

When a test node is executed, the Test Script Compiler (attolpreproC) compiles both the test scripts and the source under test. This preprocessing creates a .tdc file. The resulting source code generates a test driver.

If any Runtime Analysis tools are associated with the test node, then the source code is also instrumented with the Instrumentor (attolcc1) tool.

The test driver, TDP, stubs and dependency files all make up the test harness.

The test harness interacts with the source code under test and produces test results. Test execution creates a .rio file.

The .tdc and .rio files are processed together the Component Testing Report Generator (attolpostpro). The output is the .xrd report file, which can be viewed and controlled in the OneTest Embedded GUI.

Of course, these steps are mostly transparent to the user when the test node is executed in the OneTest Embedded GUI.

 

To learn about

See

General information on the Component Testing feature

Component Testing for Ada Overview

Writing test scripts for your software under test

Writing a Test Script

The types of source files under test

Integrated, Simulated and Additional Files

Configuration Settings for Component Testing test nodes

Component Testing for C Settings

Viewing Component Testing for C test results

Viewing Reports

Upgrading from a pre-2002 version of OneTest Embedded

Importing V2001 Component Testing Files

 

Related Topics

Using Test FeaturesActivity WizardsManually Creating a Test or Application NodeAbout HCL OneTest EmbeddedAbout System Testing for C