Studio:Using Scripts to Automate Software Testing

Much of what software developers generally dislike about testing can be overcome with better automation. Not only does automation reduce repetition, it will also help to ensure the accuracy and repeatability of tests. Because STRIDE makes your embedded application's interfaces accessible in the scripting language of your choice, using scripts is an ideal way to better automate testing.

The subject of this topic defines how to use scripts to supply inputs to a function, component, or application over one or more interfaces. These interfaces can be messaging-based or function-based. In STRIDE terminology, the script tends to be the User of the interface or interfaces. (In contrast, Using Scripts to Simulate Missing Software Units tends to involve scripts that are the Owner of an interface or interfaces.)

Via its objects, methods, and properties, ascript is the bridge between the interfaces in your embedded application and your favorite scripting language. A complete list of the objects, methods, and properties for use in your scripts can be found in the Online Help installed with STRIDE Studio. The objective of this topic is to focus on those objects, methods, and properties you will need to automate the testing of your software.

Note: To test a function, component, or application using a script, the corresponding interface(s) must be [accessible to STRIDE]. In addition, you will need an [intercept module] if any of the interfaces cross platform boundaries.

# this is a test