Difference between revisions of "Types of Testing Supported by STRIDE"

From STRIDE Wiki
Jump to: navigation, search
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
= Overview =
+
== Overview ==
  
−
One of the questions that should be asked is ''what is the '''value''' of the test?''. If the test does not discover any defects or does not provide ongoing regression than the value is questionable. Also ''what is the '''effort''' in implementing the test?''. STRIDE has been uniquely designed to support maximizing the '' '''value''' '' of the test while minimizing the '' '''effort''' '' to implement it.
+
One of the questions that should be asked is ''what is the '''value''' of the test?'' If the test does not discover any defects or does not provide ongoing regression, then the value is questionable. Also ''what is the '''effort''' in implementing the test?'' STRIDE has been uniquely designed to support maximizing the '' '''value''' '' of the test while minimizing the '' '''effort''' '' to implement it.
  
 
The STRIDE test system supports three general types of testing:
 
The STRIDE test system supports three general types of testing:
 
* '''Unit Testing'''
 
* '''Unit Testing'''
 
* '''API Testing'''
 
* '''API Testing'''
−
* '''Behavior Testing'''
+
* '''Integration Testing'''
  
 +
== Unit Testing ==
 +
'''Unit Testing''' is supported following the model found in typical [http://en.wikipedia.org/wiki/XUnit xUnit-style] testing frameworks. STRIDE also offers a number of [[Test_Units_Overview | additional features]] optimized for testing embedded software.
  
−
= Unit Testing =
+
Traditional '''Unit Testing''' presents a number of challenges in testing embedded software:
−
[[Test Units Overview | STRIDE Unit Testing]] supports the general model found in typical [http://en.wikipedia.org/wiki/XUnit xUnit-style] testing frameworks. STRIDE also offers a number of [[Test API | additional features]] optimized for testing embedded. But traditional '''Unit Testing''' does present a number of challenges for testing embedded software:
 
  
−
* Testing functions/class in '''isolation''' requires a lot of extra work, especially if not designed upfront
+
* Testing functions/classes in '''isolation''' requires a lot of extra work, especially if your software was not designed upfront for testability
−
* Testing legacy software might have very limited value (i.e. can't find any defects)
+
* The software is often not well suited for '''others''' to participate in the test implementation, since there is too much internal knowledge required to be productive
−
* Typically not well suited for '''others''' to participate in the test implementation (too much internal knowledge required)
+
* It can be difficult to automate execution of the full set of tests on the real target device
−
* Can be difficult to automate execution of the full set of tests on the real target device
 
  
 +
'''Unit Testing''' legacy software may have limited value, particularly if the software is stable with respect to defects. The best ''return-of-effort'' is often experienced when focused on '''brand new''' software components.
  
−
= API Testing =
+
== API Testing ==
−
STRIDE supports '''API Testing''' leveraging the same [[Test Units Overview | techniques]] available for Unit Testing. The difference is the focus of API Testing, which often has a better ''return-on-effort''. API Testing traditionally is about driving well-defined public interfaces. The design of ''public interfaces'' typically lends itself to testing in isolation ''without'' implementing special test logic (i.e. no stubbing required). Also public APIs are most likely documented. As a result, ''others'' can more easily participate in the test implementation. Although API Testing often represents a smaller percentage of the software being exercised, the '''value''' and '''effort''' required is well understood.
+
STRIDE supports '''API Testing''' by leveraging the same [[Test Units Overview | techniques]] available for Unit Testing.  
  
 +
'''API Testing''' differs from unit testing in that the tests focus on direct testing (calling) of a well-defined interface.
 +
 +
* The design of ''public interfaces'' often lends itself to testing in isolation ''without'' implementing special test logic (i.e. no stubbing required), which make the test implementation simpler.
 +
* Public APIs are most likely documented and as a result, ''non domain experts'' can more easily participate in the test implementation
  
−
= Behavior Testing =
+
Although '''API Testing''' often represents a smaller percentage of the software being exercised, this kind of testing is typically well understood, easy to scope, and often has a better ''return-on-effort''.
−
STRIDE supports '''Behavior Testing''' which 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. To learn more about the uniqueness of Behavior Testing click [[What_is_Unique_About_STRIDE#STRIDE_includes_behavior-based_testing_techniques | '''here''']]. We believe that Behavior Testing has a very high ''return-on-effort'' and can be easily deployed into legacy software systems.  
 
  
−
Some of the advantages of '''Behavior Testing''':
+
== Integration Testing ==
−
* Test with fully functional software builds (no isolation issues)
+
STRIDE also supports '''Integration Testing''', which is different than Unit Testing or API Testing in that it does not focus simply on calling functions and validating return values. To learn more about some of the unique testing techniques well suited for this type of testing [[What_is_Unique_About_STRIDE#Expectations | '''read here''']].
−
* Applies to a large percentage of the software
+
 
−
* Can execute with functional and black-box testing
+
'''Integration Testing''' focuses on validating a larger scope of the software while executing under normal operating conditions.
−
* Easy to add [[Test Point | Test Points]] to provide coverage
+
 
−
* Others can easily participate in test implementation
+
* Tests are performed typically with fully functional software build
−
* Test can be written using [[Perl_Script_APIs#STRIDE::Test | scripting on the host]] and [[Expectation_Tests_in_C/C%2B%2B | native target code]]
+
* There are minimal code isolation challenges
−
* Validation is fully automated (not done manually by tribal experts)
+
* Test results provide a sanity check on the health the software
−
* Design knowledge is extracted and made available to other team members via [[Source Instrumentation Overview | instrumentation]]
+
 
−
* Very useful for continuous integration
+
We believe that '''Integration Testing''' has a very high ''return-on-effort'' and is more applicable to legacy software systems.
  
  
 
[[Category: Overview]]
 
[[Category: Overview]]

Latest revision as of 10:13, 4 November 2010

Overview

One of the questions that should be asked is what is the value of the test? If the test does not discover any defects or does not provide ongoing regression, then the value is questionable. Also what is the effort in implementing the test? STRIDE has been uniquely designed to support maximizing the value of the test while minimizing the effort to implement it.

The STRIDE test system supports three general types of testing:

  • Unit Testing
  • API Testing
  • Integration Testing

Unit Testing

Unit Testing is supported following the model found in typical xUnit-style testing frameworks. STRIDE also offers a number of additional features optimized for testing embedded software.

Traditional Unit Testing presents a number of challenges in testing embedded software:

  • Testing functions/classes in isolation requires a lot of extra work, especially if your software was not designed upfront for testability
  • The software is often not well suited for others to participate in the test implementation, since there is too much internal knowledge required to be productive
  • It can be difficult to automate execution of the full set of tests on the real target device

Unit Testing legacy software may have limited value, particularly if the software is stable with respect to defects. The best return-of-effort is often experienced when focused on brand new software components.

API Testing

STRIDE supports API Testing by leveraging the same techniques available for Unit Testing.

API Testing differs from unit testing in that the tests focus on direct testing (calling) of a well-defined interface.

  • The design of public interfaces often lends itself to testing in isolation without implementing special test logic (i.e. no stubbing required), which make the test implementation simpler.
  • Public APIs are most likely documented and as a result, non domain experts can more easily participate in the test implementation

Although API Testing often represents a smaller percentage of the software being exercised, this kind of testing is typically well understood, easy to scope, and often has a better return-on-effort.

Integration Testing

STRIDE also supports Integration Testing, which is different than Unit Testing or API Testing in that it does not focus simply on calling functions and validating return values. To learn more about some of the unique testing techniques well suited for this type of testing read here.

Integration Testing focuses on validating a larger scope of the software while executing under normal operating conditions.

  • Tests are performed typically with fully functional software build
  • There are minimal code isolation challenges
  • Test results provide a sanity check on the health the software

We believe that Integration Testing has a very high return-on-effort and is more applicable to legacy software systems.

Retrieved from "https://www.stridewiki.com/index.php?title=Types_of_Testing_Supported_by_STRIDE&oldid=13029"