Testwell CTC++ Test Coverage Analyser
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
PCLTA-21 PCI Network Adapter Models 74501, 74502, 74503, and 74504
PCLTA-21 PCI Network Adapter Models 74501, 74502, 74503, and 74504 ▼ Universal 32-bit PCI adapter card for LONWORKS® networks for PCs with 3.3V or 5V PCI ▼ Plug-and-play network driver compatible with MicrosoftWindows® 98/2000 and Windows XP ▼ Downloadable firmware allows updates without accessing or changing hardware ▼ Integral FT 3150® Free Topology Smart Transceiver, RS-485, TPT/XF-78, or TPT/XF-1250 transceiver ▼ LNS® Network Services Interface (NSI) supports LNS applications ▼ Layer 5 MIP for use with OpenLDV™ driver Description ▼ CE Mark, U.L. Listed, cU.L. Listed The PCLTA-21 Network Adapter is a high-perform- ance LONWORKS interface for personal computers equipped with a 3.3V or 5V 32-bit Peripheral The NSI mode of the PCLTA-21 adapter is used Component Interconnect (PCI) interface and a compati- with applications based on the LNS network operating system such as the LonMaker Tool, or the LNS DDE ble operating system. Designed for use in LONWORKS control networks that require a PC for monitoring, Server. managing, or diagnosing the network, the PCLTA-21 The MIP mode of the PCLTA-21 adapter is used with adapter is ideal for industrial control, building automa- applications based on OpenLDV. tion, and process control applications. The PCLTA-21 In both NSI and MIP modes, the adapter permits the adapter features an integral twisted pair transceiver, host PC to act as a LONWORKS application device, such downloadable memory, a network management inter- that the PC is running application-specific programs face, and plug-and-play capability with Microsoft while the adapter handles lower layer functions such as Windows 98/2000 and Windows XP. -
Systematic Testing of the Continuous Behavior of Automotive Systems
Systematic Testing of the Continuous Behavior of Automotive Systems Eckard Bringmann Andreas Krämer DaimlerChrysler DaimlerChrysler Alt-Moabit 96a Alt-Moabit 96a 10559 Berlin, Germany 10559 Berlin, Germany +49 30 39982 242 +49 30 39982 336 [email protected] [email protected] ABSTRACT gap, the testing of automotive systems in practice focuses on In this paper, we introduce a new test method that enables the simple data tables to describe input signals or on script languages, systematic definition of executable test cases for testing the such as Visual Basic, Python or Perl, to automate tests. continuous behavior of automotive embedded systems. This Nevertheless, signals are still very difficult to handle in these method is based on a graphical notation for test cases that is not languages. Even worse, there is no systematic procedure to help only easy to understand but also powerful enough to express very testers reveal redundancies and missing, test relevant, aspects complex, fully automated tests as well as reactive tests. This new within their test cases. In other words, the selection of test data approach is already in use in several production-vehicle occurs ad hoc and is based on some use cases and typical extreme development projects at DaimlerChrysler and at some suppliers. scenarios but often does not cover all functional requirements of the system under test (SUT). Categories and Subject Descriptors Our new approach – which is called Time Partition Testing D2.5 [Software Engineering]: Testing -
Automated Unit Testing in Model-Based Embedded Software Development
Automated Unit Testing in Model-based Embedded Software Development Christoph Luckeneder1, Hermann Kaindl1 and Martin Korinek2 1Institute of Computer Technology, TU Wien, Vienna, Austria 2Robert Bosch AG, Gollnergasse¨ 15-17, Vienna, Austria Keywords: Automated Testing, Unit Tests, Model-based Development, Embedded Software, Safety-critical Systems, Automotive. Abstract: Automating software tests is generally desirable, and especially for the software of safety-critical real-time systems such as automotive control systems. For such systems, also conforming with the ISO 26262 standard for functional safety of road vehicles is absolutely necessary. These are embedded systems, however, which pose additional challenges with regard to test automation. In particular, the questions arise on which hardware platform the tests should be performed and by use of which workflow and tools. This is especially relevant in terms of cost, while still ensuring conformance with ISO 26262. In this paper, we present a practical approach for automated unit testing in model-based embedded software development for a safety-critical automotive application. Our approach includes both a workflow and sup- porting tools for performing automated unit tests. In particular, we analyze an as-is workflow and propose changes to the workflow for reducing costs and time needed for performing such tests. In addition, we present an improved tool chain for supporting the test workflow. In effect, without manually implementing each test case twice unit tests can be performed both in a simulation environment and on an open-loop test environment including the embedded platform target hardware. 1 INTRODUCTION The following support through a tool chain was planned: modeling and simulation of the resulting Automotive systems have more and more become software models, as well as model-based test automa- software-intensive systems, which include large-scale tion. -