News

QA-MISRA 26.04: Faster Analysis, Smarter Reporting, Greater Flexibility

The new release delivers significant improvements in performance, reporting accuracy, and workflow flexibility for teams developing safety- and business-critical software. It introduces ...

Cantata 26.04: Bringing AI-Assisted Testing into the Verification Workflow

The new release introduces new AI-assisted testing capabilities, enhanced automation, and greater flexibility for teams developing safety-critical C and C++ software. Highlights include...

Shift-Left Embedded Software Quality: Finding Defects Before Testing

In embedded software development, defects discovered during integration, system testing, or field validation often become significantly more expensive to resolve than those identified during implementation. Industry studies suggest that fixing defects late in the development lifecycle can cost 10 to 100 times more than addressing them earlier, resulting in increased debugging effort, delayed releases, and higher project risk.   Unlike traditional software applications, embedded systems introduce additional complexity through hardware interactions, real-time constraints, communication protocols, and safety requirements. For example, a runtime defect identified during hardware integration may require extensive debugging across software, drivers, and target hardware, whereas the same issue discovered during development can often be resolved much more efficiently.   This is why many engineering organizations are adopting a shift-left approach to software quality. Shift-left development focuses on moving verification activities earlier in the development process, allowing teams to identify and resolve issues before they reach integration and system validation stages.   A practical shift-left strategy for embedded software combines coding standards enforcement, static analysis, and automated unit testing.   Using QA·MISRA, development teams can automatically enforce MISRA coding guidelines during implementation, helping improve code quality and reduce reliance on manual code reviews.   With Astrée, engineers can perform deep static analysis to identify potential runtime issues such as arithmetic overflows, invalid memory accesses, and uninitialized variables without requiring execution on target hardware.   Finally, Cantata enables automated unit testing, code coverage analysis, and early validation of software behavior before full system integration begins.   A modern embedded verification workflow may therefore follow this sequence:   Develop → QA MISRA → Astrée → Cantata → Integration Testing → System Testing   By introducing verification activities earlier in the development lifecycle, embedded teams can reduce defect escape rates, shorten debugging cycles, improve software reliability, and increase confidence in project schedules and product releases. Rather than treating quality as a final-stage activity, shift-left development transforms software verification into a continuous engineering practice.   To learn more about our embedded software quality solutions, please contact Hrutik Champaneri at hrutik.champaneri@joraltechnologies.com   Register HERE for our upcoming webinar to see Astrée static analysis integrated directly into Visual Studio Code.

VS Code and the Modern Embedded Workflow

Visual Studio Code has become a preferred development environment for many embedded software teams thanks to its flexibility, lightweight design, and extensive extension ecosystem. However, as embedded projects grow in complexity, writing code is only part of the challenge. Teams must also ensure software quality, compliance, test coverage, and verification while still meeting aggressive release schedules. The challenge is that many of these activities are still performed later in the development lifecycle, where defects become significantly more expensive to resolve. Industry studies have shown that software defects discovered during integration or system testing can cost up to 10x more to fix than those identified during development. For this reason, many organizations are shifting verification activities earlier in the software lifecycle to reduce project risk, improve quality, and avoid costly rework. Rather than forcing developers to abandon their preferred development environment, a modern VS Code-based workflow allows quality and verification activities to be integrated directly into day-to-day development. Developers can use Keil MDK to build and debug Arm Cortex-M applications while continuing to work within a familiar VS Code environment. Powered by Arm Compiler and the CMSIS ecosystem, Keil MDK provides optimized code generation, comprehensive device support, and advanced debugging capabilities specifically designed for Arm-based systems. This enables teams to accelerate development while building on a trusted toolchain widely used across safety, industrial, automotive, and IoT applications. Coding standards compliance is often another source of engineering effort, particularly for projects operating under safety, security, or regulatory requirements. QA MISRA helps identify coding standard violations as code is written, allowing issues to be corrected before formal reviews begin. Organizations that introduce coding standards verification earlier in development often report reduced review effort, improved code consistency, and fewer compliance related surprises during audits and certification activities. With the QA·MISRA extension integrated directly into VS Code, developers can identify violations and receive feedback within the editor, helping them address issues before they become larger development or compliance challenges. Static analysis provides another opportunity to identify defects before they become schedule impacting problems. AbsInt Astrée analysis tools help detect runtime anomalies, stack usage concerns, and software defects before code reaches target hardware. Finding issues during development rather than during integration testing can substantially reduce debugging effort while improving software reliability and reducing verification risk. Similar to QA MISRA, Astrée integrates with VS Code and highlights analysis results directly within the development environment, enabling engineers to identify and resolve issues earlier in the software lifecycle. Verification through testing remains equally important. QA Systems Cantata enables automated unit and integration testing for C and C++ applications, helping teams continuously verify functionality throughout development. Studies have shown that automated testing can reduce manual test execution effort by 30–50% while improving repeatability, coverage, and traceability. For organizations operating in regulated industries, automated testing also helps generate evidence required for standards such as ISO 26262, IEC 61508, IEC 62304, and DO-178C. With Cantata's VS Code integration, developers can generate test cases, execute tests, and review code coverage directly within their development environment, helping teams build quality into the software lifecycle from the start. Modern development workflows increasingly rely on CI/CD pipelines to improve efficiency, consistency, and software quality. VS Code integrates seamlessly with source control and automation platforms, making it easier to manage branches, reviews, builds, testing, and deployments. When combined with tools such as Keil MDK, QA·MISRA, AbsInt, and Cantata, teams can automate quality checks, compliance verification, static analysis, compilation, and testing throughout the development lifecycle. This unified workflow improves traceability, strengthens collaboration between development and quality teams, and helps identify issues earlier, reducing the risk of costly late-stage defects while providing greater confidence that software meets quality, security, and compliance requirements before release.   Together, VS Code, Keil MDK, QA MISRA, AbsInt, and Cantata support multiple stages of the embedded software V-model from implementation and debugging through compliance, static analysis, testing, and verification. The result is not simply better tooling, but a more predictable development process, fewer escaped defects, reduced rework, and higher confidence in software quality before release. Interested in learning how these tools can fit into your development workflow? Reach out to Hrutik Champaneri at hrutik.champaneri@joraltechnologies.com to discuss your project requirements, compliance goals, or embedded software development challenges.   Explore our VS Code Ecosystem page to discover tools for embedded development, static analysis, MISRA compliance, automated testing, and CI/CD integration, all within a modern VS Code workflow.  

Safe and Efficient AUTOSAR Development with ISO 26262 Verification

AUTOSAR defines how software is structured. QA Systems tools prove that the software is safe. AUTOSAR provides a standardised software architecture that underpins much of today’s automotive ECU development. While it delivers structural consistency and standardised interfaces, functional safety certification is determined by how the underlying C/C++ software is verified and not by architecture alone. When combined with rigorous static and dynamic verification, it enables OEMs and Tier 1 suppliers to achieve ISO 26262-compliant, ASIL-aligned software verification across powertrain, chassis, ADAS, and software-defined vehicle platforms.   Why AUTOSAR Alone Is Not Enough for ISO 26262   ISO 26262 compliance is achieved through rigorous software verification, regardless of whether a project uses Classic or Adaptive AUTOSAR. This includes:   Mandatory coding-standard compliance Unit and integration testing Structural coverage, including MC/DC at higher ASILs Full traceability and audit-ready evidence   This is where QA-MISRA and Cantata integrate directly into AUTOSAR workflows, providing the static and dynamic verification evidence required to support ISO 26262 safety cases.   Where AUTOSAR Is Used in Safety-Critical Automotive Systems   Classic AUTOSAR Domains:   Powertrain ECUs (torque control, fuel injection, emissions) Braking, steering and chassis systems (ABS, ESC, EPB, steer-by-wire)   Adaptive AUTOSAR Domains:   ADAS and automated driving controllers (AEB, ACC, LKA) Software-defined vehicle platforms, OTA, V2X, EV energy management   Modern vehicles often combine Classic ECUs for actuation with Adaptive controllers for perception and planning, creating end-to-end safety-critical chains from sensor to actuator.   Using QA-MISRA in an AUTOSAR Workflow   QA-MISRA provides static analysis and coding-standard enforcement aligned with ISO 26262 Part 6 for AUTOSAR software implementation. It analyses:   MISRA C MISRA C++ AUTOSAR C++14   This ensures that BSW drivers, RTE glue code, and SWCs avoid undefined behaviour, data races, memory errors, and unsafe constructs. Typical QA-MISRA AUTOSAR Flow   Generated and handwritten C/C++ is analysed in CI pipelines Project-specific rule profiles are derived from ASIL targets and HARA The QA-MISRA Tool Qualification Support Kit (QSK) provides ISO 26262 tool-confidence evidence   Benefits:   Reduced manual code reviews Early detection of integration regressions Consistent enforcement across multi-supplier AUTOSAR projects   Using Cantata to Verify AUTOSAR Components   Cantata provides ISO 26262-aligned dynamic unit and integration testing and is independently certified for use up to ASIL D. Typical Cantata Applications in AUTOSAR   Unit testing of safety-critical SWCs (e.g. brake pressure control, steering assist, torque arbitration) Using RTE and BSW stubs to achieve: statement coverage branch coverage MC/DC coverage   Integration testing of end-to-end safety chains (e.g. sensor fusion → motion control → brake/steering actuation) on target hardware   Cantata’s TÜV certification and ISO 26262 qualification kits provide regulators with confidence that test results can be relied upon in the safety case.   Bringing It All Together for Safety-Critical Projects   A pragmatic and certifiable approach for safety-critical automotive development is:   AUTOSAR → architectural backbone QA-MISRA → static verification & defect prevention Cantata → dynamic verification, coverage & regression   AUTOSAR defines the structure. QA-MISRA and Cantata provide the verification evidence that the C/C++ implementation is robust, compliant, and tested to ASIL-appropriate coverage levels.   AUTOSAR Classic vs Adaptive: How QA Systems Maps Across Both   QA Systems tools operate horizontally across both Classic and Adaptive AUTOSAR. They do not replace AUTOSAR services, they verify the software that implements them.   AUTOSAR Classic: Control-Centric ECUs   Used for powertrain, chassis, airbags, EPS, and body ECUs.   QA-MISRA enforces MISRA/AUTOSAR coding rules and provides ISO 26262 tool-qualification evidence Cantata performs unit and integration testing of SWCs and BSW using RTE/MCAL stubs, certified up to ASIL D   AUTOSAR Adaptive: Service-Oriented Platforms   Used for ADAS, central compute, connectivity, OTA, and domain controllers.   QA-MISRA enforces safe C++ coding across complex Adaptive services Cantata validates safety-relevant shared libraries and services using structural coverage, regression testing, and fault-response validation   Cross-Cutting ISO 26262 and Tool Qualification   Classic and Adaptive AUTOSAR share the same ISO 26262 tool-qualification requirements.   Cantata: TÜV-certified (ISO 26262 TCL 1, up to ASIL D) QA-MISRA: ISO 26262 Tool Qualification Support Kit   Together they provide the complete tool-confidence argument required by OEMs and Tier 1 suppliers.   Practical Mapping Summary   Classic domain: powertrain, chassis, airbags, EPS → verify low-level C code with QA-MISRA + Cantata, apply MC/DC where required Adaptive domain: ADAS, central compute, connectivity, OTA → verify C/C++ services with QA-MISRA for defect prevention and Cantata for regression & safety-mechanism testing.   © 2026 QA Systems. Published by JORAL Technologies.

Cantata Now Available as a VS Code Extension

Hello Engineering Team,   My name is Hrutik from the JORAL Engineering Team.   QA Systems Cantata, a trusted solution for unit testing and code coverage, is now expanding its accessibility with a new Visual Studio Code extension. Known for helping teams automate testing, run efficient test execution, and generate clear diagnostic reports, Cantata helps development teams detect issues early and improve software quality with confidence.   Just a quick note to let you know that Cantata is now available as an extension pack for Visual Studio Code.   With this latest update, developers can now use Cantata directly within VS Code while still benefiting from the full functionality traditionally available in the Cantata IDE. This integration makes it easier for teams already working in VS Code to adopt Cantata without changing their workflow, improving efficiency and accessibility.   To get started:   Open Visual Studio Code Go to the Extensions tab Search for “Cantata” You should see a set of Cantata-related extensions—install the ones you need   If you’d like to see how Cantata works within VS Code, I’ve included a short demo video for reference:   🎥 Cantata Visual Studio Code Extension Demohttps://www.youtube.com/watch?v=HClll6OWOWg&list=PL-3AenM-IauNUzUAE5SxDm1fboHdHobXr   Feel free to reach out if you have any questions or would like a walkthrough.     Hrutik Champaneri Field Application Engineer Email: hrutik.champaneri@joraltechnologies.com https://www.linkedin.com/in/hrutikchampaneri/ https://joraltechnologies.com/

Canata 26.01 AI-Assisted Test Generation for Cantata

We hope you have had a good start to the new year! As promised, we are delighted to announce the release of Cantata 26.01, featuring the innovative AI-Assisted Test Generation and a new Visual Studio Code Extension     Cantata 26.01 now available     AI-Assisted Test Generation for Cantata   Cantata 26.01 introduces the Cantata Test Automation Skill: a new integration that brings AI-assisted test generation into your Cantata workflow. By combining Cantata's proven testing framework with the capabilities of Claude Code (Anthropic's agentic coding tool), this skill enables developers to generate unit tests for C/C++ source code using natural language commands.   Visual Studio Code Extension The new VS Code extension in Cantata 26.01 allows the creation of Cantata test scripts directly within the IDE, featuring a fresh new user interface and extensive configurability. To create a new test script, developers start by opening the test script configuration view. Within this interface, they can select the source files to be tested, define the script name, and configure other basic settings from the main configuration tab. Additional tabs provide more detailed controls, such as options for stubs and wrappers, while advanced customization is available through the extension settings for even greater control over the test script.     Check out our demo videos on the new features   Cantata AI-Assist Cantata VS Code Extensions     Further technical details can be found here:   Technical Note - Integration with Claude CodeCantata 26.01 Release Notes

Functional Safety in Automotive: ISO 26262 Testing Best Practices

Functional safety is a non-negotiable requirement in modern automotive software development. ISO 26262 provides the regulatory framework to ensure reliability and effective risk management across vehicle electronic and electrical (E/E) systems. To meet these demands, certified tools from QA Systems, Cantata and QA-MISRA, form the backbone of robust ISO 26262 testing strategies, enabling rigorous verification, automation, and full traceability for projects targeting Automotive Safety Integrity Levels (ASIL) up to D, the highest integrity tier for critical systems such as autonomous braking and airbag deployment.     ISO 26262 Testing Principles   ISO 26262 defines a structured, lifecycle-driven verification process that begins with hazard classification and ASIL determination and continues through: requirements definition and bidirectional traceability unit and integration testing fault injection and robustness testing structural and code coverage analysis   For example, in Level 4 Autonomous Emergency Braking (AEB) systems, the lifecycle starts with item definition and Hazard Analysis and Risk Assessment (HARA), followed by measurable safety requirements mapped directly to verification activities. This disciplined approach has been critical in preventing failures such as unintended acceleration, incidents that historically led to major recalls and industry-wide safety reforms.     QA Systems: Enabling ISO 26262 Compliance   Cantata   SGS-TÜV independently certified for use up to ASIL D, Cantata automates: unit and integration test generation branch and MC/DC structural coverage requirements-based testing fault-injection and robustness validation Cantata directly supports the confirmation review phase of ISO 26262, where independent assessors validate the effectiveness of implemented safety measures.     QA-MISRA   QA-MISRA complements Cantata by providing: automated static code analysis enforcement of MISRA C/C++ coding standards tool qualification kits for compliance reporting early detection of unsafe language constructs and resource usage Together, Cantata and QA-MISRA deliver a certified workflow that supports ISO 26262 requirements across all ASIL levels.     Real-World Testing Examples   Emergency Braking Systems (AEB): Automotive OEMs use Cantata to simulate sensor faults, actuator failures, and unexpected vehicle maneuvers, verifying that embedded software consistently responds within defined safety limits. QA-MISRA ensures the underlying ADAS codebase complies with MISRA rules to prevent undefined behavior before deployment.   Electronic Throttle Control: In one documented case, ISO 26262 verification activities uncovered shortcomings in functional safety implementation, prompting revised software architectures and significantly strengthened validation processes.     ISO 26262 Testing Best Practice   To build a defensible functional safety case, automotive organisations should:   establish bidirectional traceability between requirements, tests, and results   adopt automation for regression, fault injection, and interface testing   maintain comprehensive documentation using certified tools (Cantata and QA-MISRA) to streamline independent confirmation reviews   integrate simulation methodologies (MIL, SIL, HIL) to validate fault behaviour and edge cases   continuously update safety plans and audits to reflect new risks, technologies, and regulatory updates   By combining these best practices with QA Systems’ proven toolsets, automotive teams can confidently meet ISO 26262 requirements, safeguard public trust, and protect road users against the evolving risks of embedded vehicle systems.       Mapping QA Systems Tools to Unit, Integration, and System Testing   QA Systems tools align precisely with the classic software testing pyramid: unit, integration, and system testing.   Unit Testing   Cantata is purpose-built for automated unit testing of embedded C and C++ software. It enables verification of individual functions or modules in isolation using:   white-box testing techniques branch and MC/DC code coverage full requirements traceability   Key capabilities include automatic test case generation, stubbing, and mocking, ensuring dependencies are controlled and each test focuses strictly on the logic under test, fully aligned with ISO 26262 expectations.   Integration Testing   Cantata extends seamlessly into integration testing by allowing multiple modules, subsystems, and APIs to be verified together. It supports:   call interception and wrapping controlled fault injection interaction and interface validation   This ensures that not only do individual components behave correctly in isolation, but that data flows, error handling, and interfaces remain robust, as required for ISO 26262 item integration.   System Testing   While Cantata focuses primarily on unit and integration levels, its outputs form the foundation of system-level qualification evidence. For full system validation:   Cantata provides low-level dynamic test and coverage evidence QA-MISRA supplies coding-standard compliance evidence Both tools contribute traceable, auditable artefacts required for final system certification   Together, they ensure that system-level safety is built on verified, standards-compliant software from the earliest phases of development.     Summary Table     Test Level Main QA-Systems Tool Capability Highlight Unit Testing Cantata Isolate modules, auto-generate tests, and coverage analysis Integration Testing Cantata Combine modules, wrap/call intercept, interface testing System Testing Cantata & QA-MISRA Evidence & compliance for system qualification     Together, Cantata and QA-MISRA provide end-to-end ISO 26262 verification, from precise code-level correctness to system-level safety assurance with certification-ready evidence.     © 2025 QA Systems. Published by JORAL Technologies.

DO-278A and the Importance of a Qualifiable Toolchain for Aerospace Software

  Developing safety-critical C and C++ software for air traffic management or aerospace systems under DO-278A demands the highest level of reliability and verification rigour.A qualifiable toolchain for aerospace software, combining static analysis, dynamic unit testing, and code coverage, is essential to meet the standard’s requirements for traceability, compliance, and software assurance.     Why a Qualifiable Toolchain for Aerospace Software is Essential   Early Defect Detection & Compliance: Static analysis tools identify vulnerabilities and standard violations (such as buffer overflows, insecure libraries, and directive violations) early, before code execution, preventing defects from propagating. This proactive approach supports DO-278A’s emphasis on defect prevention and standard conformance.   Dynamic Testing & Coverage Evidence: Dynamic unit and integration testing, together with structural coverage (statement, branch, and MC/DC), proves that requirements are correctly implemented. These metrics are essential for high-assurance levels (AL1/AL2), ensuring no hidden errors remain in safety-critical code.   Traceability & Bidirectional Verification: DO-278A requires complete traceability from requirements through implementation and testing. A qualified toolchain for aerospace software ensures every test, requirement, and code path is linked maintaining audit-ready traceability when changes occur.   Tool Qualification for Reliability: If a tool’s output influences further development or verification without manual review, tool qualification guarantees reliability. As with DO-178C, qualification ensures that tools do not introduce verification errors, preserving software integrity and certification readiness.     Benefits and Regulatory Rationale   Increased confidence in software integrity by automating error detection, remediation, and traceability.   Empirical and structural coverage data, as demanded by high-assurance AL1/AL2 software components.   Minimization of manual error and fulfilling regulatory requirements for tool usage in safety-critical development, crucial for approval and certification in aerospace and air traffic management domains.   Together, these practices ensure safe, reliable, and certifiable C/C++ software that meets DO-278A’s strict verification and traceability standards.     How to Meet These Challenges   Cantata and QA-MISRA from qa-systems.com form an expertly certified and integrated toolset for developing, testing, and qualifying safety-critical C and C++ software compliant with the DO-278A standard. This toolset is uniquely suited to accelerate safety standards compliance through automated static and dynamic analysis, comprehensive coverage metrics, and test automation capabilities critical to aerospace software development.     Why Cantata and QA-MISRA Are Ideal for DO-278A   Cantata   Automates unit and integration testing for C/C++ Supports dynamic execution on both host and embedded targets Provides code coverage analysis, regression testing, and requirements traceability TÜV-certified for the highest integrity levels, meeting DO-278A verification needs   QA-MISRA   Performs static source code analysis with 900+ compliance checks Enforces MISRA C/C++ and other safety-related coding standards Ensures zero false negatives for precise, early defect detection Complements Cantata by improving code quality before runtime testing   Together, Cantata and QA-MISRA deliver end-to-end coverage of DO-278A verification needs, from static compliance to dynamic validation, backed by certification kits and qualification documentation for efficient regulatory approval.     Applications in Aerospace and Air Traffic Management   The combined Cantata and QA-MISRA toolset is ideally suited for   Avionics Flight Control Systems: Software controlling aircraft flight surfaces and stability, requiring rigorous unit and integration testing to avoid runtime failures. Air Traffic Management Systems: Safety-critical control and communication software ensuring safe airspace operation with strict code quality and traceability demands. On-board Diagnostics and Safety Monitoring: Embedded software performing real-time monitoring and fault detection with a need for exhaustive compliance with coding standards. Mission-Critical Navigation Systems: Systems that demand flawless operation due to navigation safety requirements, verified through automated unit tests and static checks. Satellite Command and Control Software: Software in satellites controlling functions under extreme conditions, validated using these tools to ensure robust, error-free operation.   Conclusion   DO-278A compliance relies on a qualifiable toolchain for aerospace software that integrates static and dynamic verification, structural coverage, and full traceability.   Cantata and QA-MISRA deliver this capability in one certified, automated environment, enabling early defect detection, comprehensive testing, and assured qualification. Together, they provide aerospace developers with a faster, more reliable path to compliance with safety-critical software standards.   For more information about QA-MISRA and Cantata, visit qa-systems.com.     © 2025 QA Systems. Published by JORAL Technologies.