Cantata Integration with Static Analysis Tools

Cantata Integration with Static Analysis Tools

This technical explores the Cantata Makefile system and discusses options for adding further calls to the default system. This type of integration is useful for calling code analysis tools such as Helix QAC®, klocwork®, Coverity® and others. Supplemental uses are also discussed.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Hitachi Vantara’s self-driving assistant

Hitachi Vantara’s self-driving assistant

Hitachi Vantara developed the Self-Driving Assistant software for autonomous vehicles. To ensure safety and adherence to standards, they chose Cantata as their testing tool. The Cantata support for C++ and its ability to perform unit, integration, and system testing were crucial factors in the selection. Cantata clear test reports and automated processes helped identify issues and saved testing time. The end customer was satisfied, and Hitachi Vantara plans to continue using Cantata for future testing.

Automated Requirements Based Testing

Automated Requirements Based Testing

Testing based on requirements involves creating test cases that are developed from the test conditions and objectives which are derived from the requirements. This method guarantees that the tests cover the intended functionalities of the system adequately. To illustrate, requirements-based testing can be used to test particular functions or assess non-functional characteristics such as usability or reliability. By utilizing requirements as the foundation for testing, developers can create test cases that are more efficient and effective in ensuring that the system performs as expected.

Why Pay For a Unit Test Tool?

Why Pay For a Unit Test Tool?

This paper addresses the question “Why pay for a unit test tool?” by considering the Quality / Resource / Time opportunity costs of choosing an open source tool, and sets out the compelling case for investing in commercial tools.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Why Bother to Unit Test?

Why Bother to Unit Test?

This paper addresses a question often posed by developers who are new to the concept of thorough testing: Why bother to unit test? The question is answered by presenting and examining some of the common arguments made against unit testing.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

QA-MISRA Safety Manual

QA-MISRA Safety Manual

The attached QA-MISRA safety manual provides guidance on using QA-MISRA for coding standards compliance checking in safety-critical contexts. It covers qualifying QA-MISRA as a «software verification tool» and using it to check adherence with MISRA C/C++ and other coding rules.

Topics include QA-MISRA’s technical capabilities, workflow, and integration into development processes for generating evidence of coding standards verification. The manual should be used with QA-MISRA user documentation to ensure proper application of its certified components for safety-critical software.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Cantata Safety Manual

Cantata Safety Manual

The attached Cantata safety manual provides guidance on using Cantata for software testing in safety-critical contexts. It covers Cantata tool certification, the safety workflow, test case creation, test execution, and results analysis when verifying safety-related code.

The manual describes how to properly install, configure, and qualify Cantata according to various safety standards. It explains how to generate certification evidence like requirements traceability, test results, and coverage analysis. The document should be used together with Cantata user guides and standard-specific briefing papers. Following this manual will help ensure the correct use of Cantata’s certified components for safety-critical software verification.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

Cantata 9.5 Release Notes

Cantata 9.5 Release Notes

Cantata 9.5 was made generally available from November 2021. This release further extends test management of code change capabilities with integrated impact analysis for more efficient change based testing, adds new project creation for non-Eclipse environments, provides zip/tar installation, and includes various other productivity and flexibility enhancements.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.

C and C++ Software Testing. Am I Covered?

C and C++ Software Testing. Am I Covered?

C and C++ Software Testing. Am I Covered?

This Whitepaper looks at the various applications of the term ‘coverage’ in the software development industry for software written in C and C++. We look at the industry definitions of the terms, applications of the techniques in various software standards and some challenges for measuring coverage you may not have considered. We highlight how modern software testing tools (such as QA Systems, Cantata) can help speed up and monitor your testing progress with coverage.

To access this resource please fill in the form:

By submitting your information, you will gain access to this resource and receive periodic relevant event invitations, as well as information on the latest valuable embedded software testing resources from our experts. You can opt out at any time. See our privacy policy.