TETware for Realtime and Embedded Systems
Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Mobile, PDAs & Embedded Systems Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Mobile, PDAs & Embedded Systems Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1232
Printed Date: 06Jul2024 at 10:43pm
Topic: TETware for Realtime and Embedded Systems
Posted By: Anjana
Subject: TETware for Realtime and Embedded Systems
Date Posted: 03May2007 at 10:59pm
|
TETware is a Test Execution Management System that takes care of the administration, reporting and sequencing of tests and provides a single common user interface for all of the tests that you develop (more . . .). It will manage local, remote and distributed testing across a range of platforms including all UNIX, all Linux and 32-bit Microsoft Windows operating systems. That is all platforms that are POSIX.1 compliant. On any of these platforms it requires the presence of a file system, to support the TETware directory structure, and the ability to carry out multiple processing. With realtime and embedded systems this is not always the case, so TETware has been modified to support testing on realtime and embedded systems that comply with POSIX 1003.13 profiles 51 to 53 (see figure). TETware is already able to manage tests operating under profile 54 as this profile supports both a file system and multiple processing.
The required modification uses the TETware exec tool facility to run the components that would normally be run on a remote (target) system on the local (host) system In this way it acts as an agent for the test case which is actually running on the realtime system. This modification has been built on the Lite version of TETware, which is used for local testing, and so avoids the overhead of the more complex distributed TETware structure. 
Figure 2:
TETware Realtime Testing ArchitectureApart from the Exec tool this version of TETware operates just as any other. At the start of a test run the test controller reads the scenario file. It then executes the test cases described in the scenario file in the manner described in the scenario file, and the results are posted into a results file. |
|||||||||||||