LDRA/Texas Instruments collaboration results in advanced testing for functional safety platform
March 03, 2015
LDRA has joined forces with with Texas Instruments to provide automated unit testing capabilities as part of TI's SafeTI Compliance Support Packages (...
LDRA has joined forces with with Texas Instruments to provide automated unit testing capabilities as part of TI’s SafeTI Compliance Support Packages (CSPs) for the company’s Hercules microcontroller software components. SafeTI CSPs help designers comply with functional safety standards, thereby reducing verification and validation efforts so that they can focus on differentiating their industrial and automotive systems. The end result is a faster time to market.
According to the folks at LDRA, SafeTI CSPs for Hercules MCU software components make it easier for customers to comply with functional safety standards. The CSPs are now available for TI’s HALCoGen software, a graphical device configuration and driver generation tool for Hercules MCUs, and the Hercules SafeTI Diagnostic Library, a collection of software functions and response handlers for various safety features of the Hercules MCUs. Note that these advanced unit testing capabilities will be fully accessible within the framework of TI’s SafeTI CSPs.
SafeTI CSPs streamline software validation efforts and assist in achieving functional safety certification by including static analysis and dynamic analysis test results, code traceability to requirements, code coverage, and code quality metrics. LDRAunit, a complete integrated environment for automated unit test generation and management, enables customers to re-execute the included unit-level tests within their own environment in order to speed up system verification.
It enables best practices in unit testing methodology by taking the smallest piece of testable software in an application, isolating it from the remainder of the code, and determining whether it behaves as expected. Code units are tested separately before being integrated into modules and then systems to simplify the IDing of which part of the code might be failing to deliver expected results.