STRIDE Overview

Welcome to the STRIDE™ Wiki

STRIDE™ is a test infrastructure used by engineers to implement and execute tests for validating embedded software executing On-Target. STRIDE has been designed specifically for On-Target White-box Testing.

The STRIDE system consists of:

A software Framework

enabling the creation of fully automated Test Assets that repeatably verify the internal design of your software

A hosted Web Application - Test Space

for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data.

STRIDE supports three general types of testing:

• Unit Testing,
• API Testing, and
• Integration Testing.

The STRIDE Framework

Runtime

The STRIDE Framework includes a Runtime software source package that supports connectivity with the host system. It is integrated with embedded application software to enable testability to be compiled into the software with minimal impact on performance or the size of the application. The software is agnostic to the RTOS, CPU, and transport. It can be configured to support multi-processes, multi-threads, user/kernel spaces, or a simpler single application process. Typically the runtime is configured as a background thread and only executes when running tests. It provides services for testing and source instrumentation.

Runner

The Framework also contains a lightweight Runner application that is a host-based command-line utility for interactive and automated test execution. It also provides services for result publishing to our hosted web application.

Build Tools

The STRIDE Build Tools are a set of command-line utilities that integrate with your target software build process. They preprocess standard C/C++ header files that contain STRIDE test declarations to auto-generate source code comprising a custom Intercept Module. The intercept module code is then built with the Runtime to provide fixturing and harnessing test logic as part of your build image.

Testing Features

STRIDE has been designed to deliver a broad spectrum of testing capabilities that enable teams to test earlier and more effectively. Unique features such as test macros, file fixturing, and function doubling facilitate deeper test coverage of your software components.

STRIDE also provides Expectations as an added validation technique. Expectation testing is unique in that it does not focus on calling functions and validating return values. The technique rather validates the expected sequencing of the software, along with state data, executing under normal operating conditions. This can span threads and process boundaries, and even multiple targets, as the application(s) is running. Developers insert simple instrumentation macros called Test Points to enable this approach, making it especially effective for testing legacy code.

This kind of validation technique can be used to test broadly scoped scenarios that span your entire system; For example:

• Complete data flow through system components
• Communication between threads, processes, and targets
• Behavior of stacks, state machines, and drivers
• … and much more

The tests can be implemented in both native code on the target and script on the host.

STRIDE Test Space

Once tests have been implemented, they are executed using the host-based Runner application. Resulting test reports can be automatically uploaded to our web application - STRIDE Test Space. This application allows both local and distributed team members to track and collaborate on results.

Failure resolution is optimized by centralizing results and providing specific source information related to failures. Test Space also has built-in collaboration features in the form of email notification for new results and regression against a baseline as well as messaging.

---

For more details refer to the following:

---

• What is Unique About STRIDE

• Types of Testing Supported

• Frequently Asked Questions