Skip to main content

Capabilities · Testing & Validation

Tested, analysed, covered, with the evidence your assessor asks for.

Automated unit testing, static analysis, on-target MC/DC coverage, MISRA compliance, HIL and SIL test design and CI regression for embedded C and C++, on toolchains GSAS supplies and supports in India.

Start a conversationWhat we do
  1. 01 What we do
  2. 02 How we work
  3. 03 Toolchain
01 What we do

Seven ways GSAS gets embedded software tested and proved.

Safety standards ask for testing at every level of the V-model, from unit tests at the bottom to system validation at the top. Each card lights the level of the V where that work sits.

The V-model: requirements, architecture and design on the left, code and compiler at the base, unit, integration and system test on the right, with static analysis, MISRA, coverage and a CI loop around the code Requirements Architecture Design System test Integration Unit test Code COMPILER MC/DC CI 1. Unit test: Automated unit and integration testing for embedded C and C++ 1 2. Static: Static analysis of every change for security and reliability defects 2 Static 3. Coverage: Statement, branch and MC/DC coverage, measured on the target 3 Coverage 4. MISRA: MISRA C and C++ and AUTOSAR C++14 compliance 4 MISRA 5. HIL / SIL: Hardware- and software-in-the-loop system test 5 HIL / SIL 6. CI: Regression pipelines with quality gates on every commit 6 7. Compiler: Compiler validation and tool qualification evidence 7
  • 1. Unit test: Automated unit and integration testing for embedded C and C++
  • 2. Static: Static analysis of every change for security and reliability defects
  • 3. Coverage: Statement, branch and MC/DC coverage, measured on the target
  • 4. MISRA: MISRA C and C++ and AUTOSAR C++14 compliance
  • 5. HIL / SIL: Hardware- and software-in-the-loop system test
  • 6. CI: Regression pipelines with quality gates on every commit
  • 7. Compiler: Compiler validation and tool qualification evidence
Hover, tap or focus a numbered point or a card to see where each capability sits.

  1. Automated unit testing

    Test environments, test cases, on-target or simulated execution, and coverage reports, with TESSY by Razorcat as the primary tool for embedded C and C++.

    • Test environment setup with stub and driver generation
    • Systematic test design with the Classification Tree Editor
    • On-target and simulation-based execution
    • MC/DC, branch and statement coverage measurement
    • Regression automation with CI/CD integration

    TESSY · qualified by Razorcat per IEC 61508, IEC 62304, ISO 26262, EN 50128

  2. Static code analysis

    Defects caught before they become field failures: Klocwork for security-focused analysis and Perforce QAC for standards compliance, tuned so teams trust the results.

    • Klocwork for security defects: CWE Top 25, CERT, OWASP
    • Perforce QAC for MISRA C/C++ and AUTOSAR C++14
    • Checker tuning and false-positive suppression
    • Baseline thresholds and CI quality gates
    • Defect triage training and workflow set-up

    Perforce Klocwork · Perforce QAC

  3. On-target code coverage

    Hardware trace shows what actually ran on the target, without instrumenting the code. DO-178C requires MC/DC at Level A, and ISO 26262 highly recommends it at ASIL D.

    • SEGGER J-Trace PRO: MC/DC, branch and statement coverage
    • Arm ULINKpro: ETM trace with statement and branch coverage
    • Coverage reports for safety assessments
    • Gap analysis and test case augmentation
    • Closed-loop coverage with the automated unit tests

    SEGGER J-Trace PRO · Arm ULINKpro · TESSY

  4. MISRA C and C++ compliance

    Compliance baselines, tool configuration, deviation procedures and the evidence an assessor asks for, across automotive, industrial, medical and aerospace code.

    • MISRA C:2012 audits, including Amendments 3 and 4
    • MISRA C++:2023 adoption and migration from older C++ guidelines
    • Deviation records and approval workflows
    • Guideline Recategorization Plans for project-specific tuning
    • Compliance reports and evidence packages for your assessor

    MISRA and AUTOSAR tools

    Perforce QAC · Klocwork

  5. HIL and SIL test design

    Embedded software validated against plant models and real hardware interfaces, bridging the gap between unit testing and system validation.

    • HIL test bench architecture and specification
    • SIL environments with plant models
    • Stimulus and response frameworks
    • Fault injection and boundary-condition testing
    • Test automation and reporting

    Designed around your target and plant model

  6. Regression testing and CI/CD

    Every change validated: unit tests, static analysis and coverage run on every commit, with quality gates that keep non-compliant code out of production.

    • CI pipeline design for embedded test workflows
    • Jenkins, GitLab CI and GitHub Actions integration
    • Quality gates with pass and fail criteria
    • Automated test reports and trend dashboards
    • Nightly build and regression scheduling

    Klocwork · Perforce QAC · TESSY in your pipeline

  7. Compiler and tool qualification

    The tests are only as trustworthy as the toolchain. SuperTest checks C and C++ compilers against the ISO language standards, and the analysis tools carry TÜV SÜD certification or their maker’s stated qualification.

    • SuperTest: requirements-based, negative and stress tests for C and C++ compilers
    • SuperTest Qualification Suite for compiler tool confidence under ISO 26262
    • Klocwork and Perforce QAC: TÜV SÜD certified for ISO 26262 and IEC 61508
    • TESSY: qualified per Razorcat for IEC 61508, IEC 62304, ISO 26262, EN 50128
    • Licensing and qualification consulting in India

    Solid Sands · Perforce · Razorcat

02 How we work

Every commit tested, every result kept as evidence.

A CI run on one change, step by step, and the three stages GSAS works through to set it up. Hover a stage to see its steps in the run.

Plan · Run · Prove
  1. Commit Change pushed, pipeline triggered
  2. Build Target build with your toolchain
  3. Static analysis Klocwork or QAC on the change
  4. MISRA Against the project’s rule set
  5. Unit tests TESSY regression suite
  6. Coverage Statement, branch, MC/DC
  7. Gate Merge passes or is blocked

  1. 01

    Plan

    Toolchain
    Unit test, static analysis and trace tools chosen for the target and the standard
    Baseline
    MISRA compliance baselines, checker configuration and recategorisation plans
    Test design
    Systematic test cases with the Classification Tree Editor

    Toolchains GSAS supplies, deploys and supports

  2. 02

    Run

    Unit
    Test environments, stubs and drivers, on-target and simulated execution
    Static
    Checker tuning, false-positive suppression and defect triage
    System
    HIL and SIL harnesses, stimulus and response, fault injection

    Teams trained on defect triage and test workflows

  3. 03

    Prove

    Coverage
    Statement, branch and MC/DC reports, with gap analysis
    Compliance
    Deviation records and MISRA evidence for your assessor
    Gates
    CI quality gates that stop non-compliant code at the merge

    Evidence packaged for your safety assessment

Related: Functional safety · Embedded software · Security engineering · Test and measurement

03 Toolchain

The tools behind the evidence.

Every tool here is one GSAS supplies, deploys and uses. Specifications and qualification statements come from each product page, as published by the tool’s maker.

Coding standards and the analysers that check them

Standard Scope Typical domain Analysers
MISRA C:2012 and 2025 C language subset Automotive, industrial, medical Perforce QAC, Klocwork
MISRA C++:2023 C++ language subset Automotive, aerospace Perforce QAC, Klocwork
AUTOSAR C++14 Adaptive AUTOSAR C++ Automotive Perforce QAC, Klocwork
CERT C Security-focused coding Safety and security code Klocwork, Perforce QAC
CWE Top 25 Common weaknesses Connected products Klocwork, Perforce QAC

Standards guides

Partner lines on this page

04 Working together

Three ways to start, depending on your standard.

The standard you work to decides which evidence matters most. Pick yours.

  1. 01

    Automotive software

    ISO 26262 · MISRA · AUTOSAR C++14

    TESSY unit and integration testing with MC/DC, Perforce QAC for MISRA and AUTOSAR C++14, Klocwork for security defects, and coverage taken from the target ECU by hardware trace.

    ISO 26262 tools

  2. 02

    Industrial, medical and rail

    IEC 61508 · IEC 62304 · EN 50128

    Toolchains whose makers state qualification for these standards: TESSY per Razorcat, and Klocwork and Perforce QAC with TÜV SÜD certification for IEC 61508 and IEC 62304. GSAS sets them up and prepares the evidence your assessor asks for.

    IEC 61508 tools

  3. 03

    Aerospace software

    DO-178C

    For projects where MC/DC is required at Level A: requirements-based unit tests, structural coverage measured on the target by hardware trace, and compiler validation with Solid Sands SuperTest.

    DO-178C tools
05 Contact

Need tests that produce assessment evidence?

Tell us the target, the language and the standard. GSAS replies with the toolchain, the test and analysis plan and a proposal, and supports your team through to the evidence.

Discuss your project Book a demo

sales@gsasindia.com +91 80 6590 1783

Questions

Testing and validation with GSAS in India

What testing and validation work does GSAS do?

Automated unit testing, static code analysis, on-target code coverage, MISRA C and C++ compliance, HIL and SIL test design, regression pipelines and compiler qualification for embedded C and C++, using toolchains GSAS supplies and supports in India.

Is TESSY qualified for safety standards?

Razorcat qualifies TESSY for safety-related software development per IEC 61508, IEC 62304, ISO 26262 and EN 50128. GSAS supplies TESSY in India and sets up the test environments, test case design and coverage reporting around it.

Klocwork or Perforce QAC: which one do we need?

Klocwork is security-focused static analysis (CWE Top 25, CERT, OWASP) with incremental, diff-based analysis across many languages. Perforce QAC is the standards-compliance analyser for MISRA C and C++ and AUTOSAR C++14. Where a project needs both, GSAS deploys both and runs them in one pipeline.

Can you measure MC/DC on the target hardware?

Yes. SEGGER J-Trace PRO lists MC/DC, branch and statement coverage from trace, and TESSY measures MC/DC as part of unit testing. Arm ULINKpro gives statement and branch coverage from ETM trace without instrumenting the code.

Does GSAS certify our software?

No. GSAS deploys and configures the tools, runs the tests and prepares the evidence, such as coverage reports, MISRA deviation records and tool qualification material. Certification is done by your assessor or certification body.

Which CI systems do you integrate with?

Jenkins, GitLab CI and GitHub Actions, with static analysis, unit tests and coverage running on every commit and quality gates that block non-compliant code.