All pages
Jump to navigation
Jump to search
- "type info" is undefined
- "typeinfo" is undefined
- Accessing target data while processing a proxy call
- Accessing the Owner Side of a Function (API) Interface from Studio
- Accessing the User Side of a Function Interface (API) from Studio
- Advantages and disadvantages of "default" candidates
- After installing the STRIDE Runtime, what are my configuration settings?
- Allowable error log levels
- Applying pragmas up and down type chains
- Are multiple callbacks possible?
- AutoScript
- AutoScript Dynamic Objects
- AutoScript Events
- AutoScript Functions
- AutoScript Messages
- Auxiliary data
- Browser Compatibility
- Build Integration
- Build Tools
- Build a TestApp
- Building an Off-Target Test App
- C++ Only Features
- C/C++ Samples
- Callback functions in Perl scripts
- Can I use Perl's Tk package in STRIDE?
- Can I use STRIDE if my embedded code has real-time constraints?
- Can I use STRIDE together with test equipment?
- Can STRIDE marshal both data and pointers?
- Can an array be cast to a pointer?
- Casting and pointers
- Connect.pl
- Creating And Using Baselines
- Creating Projects And Test Spaces
- Creating Test Spaces
- Creating and Editing Test Spaces
- Dealing with hex in Perl
- Debugging Helps
- Delegating ISHELL SendEvent
- Deploying STRIDE on the Target
- Desktop Installation
- Distribution Files
- Error Object
- Error compiling standard libaries
- Expectation Tests in C/C++
- Expectations
- Expectations Sample
- FileTransfer Sample
- File Services Sample
- File Services Samples
- File Transfer Services
- Folder Layout
- Framework Installation
- Framework Setup
- Frequently Asked Questions About STRIDE
- Function.pm
- FunctionRemoting Sample
- Function Capturing
- Function Double
- Handling non-standard or unsupported keywords
- Handling of pointer attribute tokens
- Hello Stride Sample
- How are test cases managed?
- How are test results reported?
- How can I check which version of STRIDE I am using from a script?
- How can I discover errors in scripts invoked by RunNonBlocking()?
- How can I tell which version of a workspace is used when connected to the target at runtime?
- How do I access an array in the parameter list through Perl?
- How do I access global variables?
- How do I apply an SCL pragma to an array?
- How do I create try blocks and catch exceptions in Perl?
- How do I extract the drive letter and use it to define the location of the Perl module?
- How do I get Perl scripts to emit fatal errors when a COM error occurs?
- How do I get the return value from a script?
- How do I kill a task if the window is owned by a non-killable system task?
- How do I pass unicode data to the target using Perl?
- How do I save the temporary XML file generated by the Reporter?
- How do I speed up scripts by caching an intermediate collection/object?
- How do I start non-blocking scripts which do not use the Reporter from a Perl script?
- How do I work around variable arguments for stubs?
- How does STRIDE interact with the target?
- How does STRIDE know about my APIs and messaging interfaces?
- How does STRIDE support continuous integration?
- How does STRIDE transform the software development process?
- How does the STRIDE compiler handle zero-length arrays?
- How is STRIDE different from other software testing approaches used by developers?
- How much time and how many resources are required to get STRIDE running in a typical embedded environment?
- How to define message structures
- How to generate a preprocessor (.i) file for analysis
- How to synchronize scripts
- How to work around missing or unsupported keywords
- Indicating Pass/Fail in a Test Method
- Initialize.pm
- Installation
- Installation Overview
- Instantiating ascript when running a script outside of Studio
- Integrating the Intercept Module (IM)
- Integration Overview
- Intercept Module
- Intercept Module Sample
- Interfacing Sample
- Is hyperthreading supported in STRIDE?
- Is it possible to change the host trace buffer size?
- Linking Test Plan with results
- Linux SDK
- Listing Functions and Test Units
- Listing Test Units
- Log.pm
- Main Page
- Main Page(old)
- Manual License Activation
- Name Mangling
- Notes
- Notes, Comments and Logs
- Notifications
- Off-Target Environment
- Organizing Test Units into Suites
- Organizing Tests into Suites
- PDF Links
- Parameterized Test Units
- Perl Script APIs
- Perl Script Snippets
- Perl Test API
- Perl Test Script Template
- Perl and COM
- Platform Abstraction Layer
- Posix SDK
- Pragmas
- Pretesting Test Script
- Reference
- Reference Overview
- Referring to global stride objects
- Release Notes
- Reporter
- Reporter Sample
- Reporting Entities
- Reporting Model
- Reporting Sample
- Restrictions on discriminated unions
- Running Diagnostics With Target
- Running Tests
- Running Tests (old)
- Running and Publishing the Expectations Sample
- Running and Publishing the TestIntro Sample
- Runtime Integration
- Runtime Reference
- Runtime Test Services
- S2 Technologies Web Site
- S2sbind
- S2scompile
- S2sinstrument
- SCL Data Types
- SCL Design Requirements
- SCL Message Attributes
- SCL Overview
- SCL Pragmas
- SCL Samples
- SCL Structure
- SLAP
- STRIDE 2.1.00xx
- STRIDE 3.0.01xx
- STRIDE 3.0.02xx
- STRIDE 4.1.01x
- STRIDE 4.1.02x
- STRIDE 4.1.03x
- STRIDE 4.1.04x
- STRIDE 4.2.01x
- STRIDE 4.2.02x
- STRIDE 4.3.01x
- STRIDE 5.0.01x
- STRIDE 5.0.02x
- STRIDE Build Tools
- STRIDE Extensions for Visual Studio
- STRIDE Off-Target Environment
- STRIDE Overview
- STRIDE Overview Video
- STRIDE Release Numbering
- STRIDE Runner
- STRIDE Runtime
- STRIDE Studio
- STRIDE Test Space
- Sample Stride Target Settings
- Samples
- Samples Overview
- Scl brew class
- Scl cast
- Scl conform
- Scl func
- Scl function
- Scl msg
- Scl msg bind
- Scl ptr
- Scl ptr flist
- Scl ptr opaque
- Scl ptr sized
- Scl string
- Scl struct sized
- Scl test cclass
- Scl test class
- Scl test flist
- Scl test setup
- Scl test teardown
- Scl tracepoint
- Scl tracepoint format
- Scl union
- Scl union activate
- Scl values
- Script Overview
- Script Samples
- Script Timeout Considerations
- Script execution error messages
- Scripting Overview
- Scripting Test Units
- Sending and receiving broadcast messages in the Runtime
- Setting up your CI Environment
- Source Instrumentation Overview
- Special considerations for Python users
- Stride.exe
- Stride:How to synchronize scripts
- Stride Executable
- Stride Installation
- Stride Overview
- Stride Runner
- Stride Sandbox
- Stride System Error Logging
- Stride Training
- Target Integration Overview
- Templates
- TestCase.pm
- TestSpace Setup
- Test API
- Test CClass Sample
- Test CClass Samples
- Test Class Sample
- Test Class Samples
- Test Code Macros
- Test Documentation in C/C++
- Test Double
- Test Double Sample
- Test Double Samples
- Test Doubles
- Test Fixturing in C/C++
- Test Function List Sample
- Test Function List Samples
- Test Implementation
- Test Integration
- Test Intro Cpp Sample
- Test Intro Sample
- Test Log
- Test Macros
- Test Macros Sample
- Test Macros Samples
- Test Modules Overview
- Test Plan Template
- Test Point
- Test Point (old)
- Test Point Sample
- Test Point Samples
- Test Point Testing in C/C++
- Test Points
- Test Pragmas
- Test Runners
- Test Script
- Test Script Perl Template
- Test Scripts
- Test Space Setup
- Test Space XML Schema
- Test Spec Template
- Test Unit
- Test Unit Pragmas
- Test Unit Template
- Test Units
- Test Units Overview
- Testing with Perl
- Testspace Administration
- The communication/messaging model I use in my target application is not compliant with STRIDE
- Tracing
- Tracing on Test Points
- Training
- Training Advanced
- Training Basics
- Training Doubling
- Training Expectations
- Training File IO
- Training Fixturing
- Training Getting Started
- Training Instrumentation
- Training Overview
- Training Overview (old)
- Training Parameters
- Training Perl
- Training Running Tests
- Training Runtime
- Training Runtime API
- Training Test Macros
- Training Tests in C/C++
- Training Tests in Script
- Transferring Files
- Transport Configuration File
- Transport Server Component
- Troubleshooting Build Problems
- Types of Testing Supported by STRIDE
- Understanding SCL conflicts
- Updated Message Payload Syntax
- Uploading Test Results
- User Administration
- Using STRIDE Rules for Visual Studio
- Using Scripts to Automate Software Testing
- Using Scripts to Simulate Missing Software Units
- Using Test Doubles
- Using printf
- Using the same Group ID for multiple interfaces
- Variant Types in Perl
- Web Reports Setup
- What are some specific methodologies or efficiencies enabled by STRIDE?
- What are the advantages of STRIDE?
- What if software development begins on a host-based simulation environment before migrating to the target?
- What is "white-box integration testing"?
- What is Unique About STRIDE
- What other techniques does STRIDE support to generate test cases?
- What problem does STRIDE address?
- What software development challenges result from increased complexity?
- What to do when the Perl tag file is corrupted
- What up-front integration is required to begin using STRIDE?
- What version of ActivePerl is supported by STRIDE?
- Which Perl debuggers can be used with STRIDE?
- Why am I experiencing a performance decrease in STRIDE?
- Why am I getting "unresolved external reference" errors during the linking process?
- Why do I run out of GDI resources when I open or close application windows in Studio?
- Why do the values I see in the data column of an open target Trace View seem to be random garbage?
- Why doesn't my script engine work?
- Why don't Perl scripts run even when Script Engine shows Perl?
- Why have my scripts stopped working?
- Why is AutoSense no longer working and causing Studio to hang?
- Why is my script terminating unexpectedly?
- Why use a scripting language?
- Why won't my workspace open?
- WinMobile SDK
- Windows SDK
- Working with "default" candidates
- Working with Enumerated Types
- Working with pointers to target-resident functions
- WorkspaceRun.pl
- WorkspaceSetup.pl
- Workspace Setup