I-Logix launches code test generator

Nurenberg, Germany – Embedded Systems Conference – I-Logix Inc. has launched Statemate Magnum Automatic Test Generator (ATG). Together with the recently announced Statemate Magnum Model Checking, the product gives design engineers access to a suite of formal verification and testing tools available for embedded systems design.

Statemate MAGNUM enables design engineers to capture system requirements using UML Use Case Diagrams and then to build scenarios for each Use Case with UML Sequence Diagrams. Once the requirements capture phase is completed, the engineer can build an executable specification model of the entire system. From this model, the ATG technology is used to create a comprehensive set of tests.

These tests can be used to help validate that the specification meets the requirements, that changes to the specification do not break functionality, and that the final system, sub-systems, components and code units meet the requirements as well as the specification. These tests are automatically generated from the specification that has been proven to be correct (the ‘golden’ model) using the simulation and formal verification products sold by I-Logix.

Statemate Magnum ATG gives designers complete control over configuration management of the generated test cases. The test management facility maintains complete version control and links the tests to the proper version of a specification model.

I-Logix’ Statemate Magnum ATG has been developed as part of its strategic technology partnership with Offis Systems and Consulting (OSC) GmbH.

The product’s three goals are:

Statemate MAGNUM specification model coverage – Test cases are generated to cover all basic states and transitions of the specification model. These tests are used once the model has been proven to be correct so that, if future changes are made to the model, a complete set of regression tests may be run on it to ensure nothing has been adversely affected.

Drive to state, transition, output – Designers can select a particular basic state, transition, or output that is to be reached by a test case. One test case is generated that ends in an activation of the selected state, in a firing of the selected transition or in a toggling of the selected output, respectively. This capability is used to create tests for specific model conditions. For example, if a designer needs a test to see what happens when a light is turned on, they just tell the test generator to create a sequence that gets you to this condition. The use of this capability further reduces the time it takes both to create and execute tests for the specification and the implementation while being able to focus on particular events of the system.

Scenario-driven test case generation – In addition to the specification model, sequence diagrams can be used to describe sequences of communications of events and data between the system and its environment or between sub-systems and their environments. The goal of the scenario-driven test case generation is to compute a complete run of the design model according to the described scenario in the sequence diagram. Executing these tests on the implementation ensures that, for a given high-level scenario (e.g., a car skidding or an aeroplane landing gear deploying), the implementation both meets the specification and the original requirements.

Control Engineering Daily News DeskGary A. Mintchell, senior editor gmintchell@cahners.com

Do you have experience and expertise with the topics mentioned in this content? You should consider contributing to our CFE Media editorial team and getting the recognition you and your company deserve. Click here to start this process.