Testing and verifying in all development phases

TPT makes it possible zu test and verify embedded systems in all development phases. Whether you create a simple module test or a complex system test: TPT gives you unique possibilities to create test cases intuitively and flexible. TPT can be connected via interfaces to many well-known development tools like CANape or Lauterbach's TRACE32.

With the testing tool TPT, you can test and verify control systems on all levels and in every development phase from Simulink, TargetLink or ASCET models, to C-code, to HiL, and up to tests in a vehicle.

Test case modeling

Test cases in TPT are created with automatons and test step lists. Synthesized signals and measurement data can be integrated in the test cases. TPT is able to automatically generate test cases. Test cases created with TPT are reactive,
thus the tests can react on the system’s behavior during the test run.

Hierarchical automaton in TPT

Requirements tracing

You can import requirements to TPT and link them with test cases in order to monitor the requirements coverage. Using the assessment feature of TPT (assesslets), you can automatically check and document if the test cases fulfilled the requirements or not.

Requirements can be linked to test cases, state variants, and assesslets.

Test assessment

In TPT, test results can be automatically assessed by using assessment rules. These assessment rules can be created using a mask. More complex assessment rules can be set up in a TPT-specific script language. Thanks to the auto-completion and the extensive help in TPT, both approaches are easy to manage. Finally, a detailed and significant report is created.

Set up as assessment rule using a mask

Supported test environments

Test cases created with TPT can be executed for model-in-the-loop (MIL), software-in-the-loop (SIL), processor-in-the-loop (PIL), and hardware-in-the-loop (HIL). Thus, you only need to adapt the test cases according to the development process.
If necessary, the test cases can be executed in real-time.

Test cases created with TPT can be executed on the following test environments:

MATLAB/Simulink and TargetLink

  • Unit tests and integration
    tests of Simulink models
  • Unit tests and integration tests
    of TargetLink code in SIL and PIL
  • Automatic generation
    of test environments
  • Automatic test cases generation

C-code

  • Unit tests and integration
    tests of C-code on the PC
  • Co-simulation with further software
  • Code coverage analysis
  • Automatic test case generation

ASCET

Testing of physical and implemented models as C-code or with automatic generation of test environments in ASCET.

PIL

Tests via

  • Trace32 by Lauterbach
  • Universal Debug Engine by PLS
  • Simulink by The MathWorks
  • TargetLink by dSPACE
  • On a processor

HIL

Tests on hardware-in-the-loop (HIL) test benches like

  • dSPACE HIL
  • ETAS LABCAR
  • Simulink Realtime
  • NI VeriStand
  • Concurrent iHawk HIL
  • Customized HIL systems

CAN

  • Test execution via
    CAN busses
  • Mapping of TPT-signals
    to CAN messages
  • Measurement and
    usage of application tools
  • Test bench automation
  • Tests in vehicle

INCA and CANape

Automatic application and measurement via application tools with or without MCD-3.

CANoe

  • Automatic testing of
    CANoe configurations
  • Automatic access to CANoe
    signals and system variables

FUSION

Co-simulation of different environments, for example

  • C-code
  • Functional Mockup Units (FMUs)
  • CAN
  • INCA
  • External I/O-cards
  • Environmental models
  • System models

AUTOSAR

  • Functional tests of individual AUTOSAR software components
  • Fault injection between ports
  • Function tests of software component composites
    and their runnables
  • Automatic generation of
    test environments including communication between the ports

Vehicle tests

  • Execution of tests inside a vehicle
  • Automatic driving instructions
  • Automatic assessment

Testing safety-critical systems

When testing safety-critical systems, regulations from standards like ISO 26262 or IEC 61508 need to be taken into account. Those regulations also apply to the testing tool itself. If the testing tool is appropriate for the tests is determined in a so-called qualification. The qualification can be done by PikeTec.

Additional features

Jenkins integration

Using the Jenkins plugin by PikeTec, you can automatically run test cases created with TPT on a Jenkins continuous integration server.

Subversion integration

Versions of TPT project can be managed with Subversion (SVN)
by Apache.


Java RMI-API for TPT

With a Java-API for TPT, most functions can be controlled and invoked remotely.

Test management

With TPT, test management for TPT projects is possible. Additionally TPT provides interfaces for example to external test management tools.

...

and much more

Copyright © www.piketec.com    All rights reserved

Follow us

  • YouTube
  • LinkedIn
  • Twitter