STRIDE Overview: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<span style="#color:#0067A5"> <font size="5"> STRIDE™ Test System Overview </font> </span> | <span style="#color:#0067A5"> <font size="5"> STRIDE™ Test System Overview </font> </span> | ||
The | STRIDE™ has been designed specifically for ''On-Target White-box Testing''. STRIDE™ is a test system used for validating embedded software executing On-Target. The STRIDE™ system consists of a '' '''Framework''' '' for testing and a hosted '' '''Web Application''' '' for storing and analysing test results. | ||
The '' '''Framework''' '' includes a ''cross-platform'' [[Runtime_Reference | '''runtime''']] source package that supports connectivity with the host system and provides [[Runtime_Test_Services | '''services for testing''']] and [[Source_Instrumentation_Overview | '''source instrumentation''']]. The '' '''runtime''' '' enables testability to be compiled into the embedded software with minimal impact on performance or the size of the application. The '' '''Framework''' '' also contains a host-based [[Stride_Runner | '''runner''']] for interactive and automated test execution and publishing to our [[STRIDE_Test_Space | '''Web Application''']]. | |||
: | [[image:STRIDE 4.2.jpg | 500px]] | ||
STRIDE's test system is designed to deliver a broad spectrum of ''testing capabilities'' that enable teams to test earlier and more effectively. Developers can implement [[Test_Units_Overview | '''API and unit tests''']] in C/C++ that execute on On-Target and are controlled from the host. Unique features such as [[File_Transfer_Services | '''file fixturing''']] and [[Using_Test_Doubles | '''function doubling''']] facilitate deeper coverage of your software components. Because the '' '''Framework''' '' is ''cross-platform'', testing can also be executed using Off-Target environments such as Windows and Linux host machines. The [[Category:SDKs | '''STRIDE SDKs''']] for each host environment allow for a seamless transition between the real target and an Off-Target environment. | |||
Beyond traditional developer testing, STRIDE also provides [[Test_Modules_Overview |'''behavior-based testing techniques''']]. Behavior-based testing is different than unit testing or API testing in that it ''does not'' focus on calling functions and validating return values. Behavior testing, rather, validates the ''expected sequencing of the software'' executing under normal operating conditions. This can span threads and process boundaries, and even multiple targets, as the application(s) is running. Developers insert instrumentation [[Test_Point | '''macros''']] to enable this approach, making it especially effective for testing legacy code. This kind of ''expectation-based'' testing can be used to validate much more comprehensive and system wide testing scenarios, for example: | |||
* Data flow through system components | |||
* Communication between threads, processes, and targets | |||
* Behavior of stacks, state machines, and drivers | |||
* … and much more | |||
Once tests have been implemented, they are executed using the '' '''runner''' '' and test reports can be automatically uploaded to our '''Web application''' - [[STRIDE_Test_Space | '''STRIDE Test Space''']]. This application allows all team members to track and collaborate on results. Failure resolution is optimized by centralizing results, providing specific source information related to failures, and automatic email notification for new results. | |||
<hr/> | |||
<hr/> | <hr/> | ||
'' | '''For more details on the STRIDE Test System refer to the following:''' | ||
<font size="3"> | |||
* | * [[What is Unique About STRIDE]] | ||
* [[STRIDE FAQ | Frequently Asked Questions]] | |||
* [[STRIDE Overview Screencast]] | |||
* [[Behavior Test Example Screencast]] | |||
* [[API/Unit Test Example Screencast]] | |||
</font> | |||
<hr/> | |||
<hr/> | |||
[[Category: Overview]] | |||
Revision as of 15:41, 1 June 2010
STRIDE™ Test System Overview
STRIDE™ has been designed specifically for On-Target White-box Testing. STRIDE™ is a test system used for validating embedded software executing On-Target. The STRIDE™ system consists of a Framework for testing and a hosted Web Application for storing and analysing test results.
The Framework includes a cross-platform runtime source package that supports connectivity with the host system and provides services for testing and source instrumentation. The runtime enables testability to be compiled into the embedded software with minimal impact on performance or the size of the application. The Framework also contains a host-based runner for interactive and automated test execution and publishing to our Web Application.
STRIDE's test system is designed to deliver a broad spectrum of testing capabilities that enable teams to test earlier and more effectively. Developers can implement API and unit tests in C/C++ that execute on On-Target and are controlled from the host. Unique features such as file fixturing and function doubling facilitate deeper coverage of your software components. Because the Framework is cross-platform, testing can also be executed using Off-Target environments such as Windows and Linux host machines. The for each host environment allow for a seamless transition between the real target and an Off-Target environment.
Beyond traditional developer testing, STRIDE also provides behavior-based testing techniques. Behavior-based testing is different than unit testing or API testing in that it does not focus on calling functions and validating return values. Behavior testing, rather, validates the expected sequencing of the software executing under normal operating conditions. This can span threads and process boundaries, and even multiple targets, as the application(s) is running. Developers insert instrumentation macros to enable this approach, making it especially effective for testing legacy code. This kind of expectation-based testing can be used to validate much more comprehensive and system wide testing scenarios, for example:
- Data flow through system components
- Communication between threads, processes, and targets
- Behavior of stacks, state machines, and drivers
- … and much more
Once tests have been implemented, they are executed using the runner and test reports can be automatically uploaded to our Web application - STRIDE Test Space. This application allows all team members to track and collaborate on results. Failure resolution is optimized by centralizing results, providing specific source information related to failures, and automatic email notification for new results.
For more details on the STRIDE Test System refer to the following: