Training Overview (old)
Our training approach is based on articles (here in the wiki) and on a set of code samples that readily execute in our off-target (desktop) environment. Our training focuses on a self-guided tour of the product using the samples we provide as the primary study material. Please review the sections below before proceeding to the specific training topics.
Prerequisites
In order to build and execute the samples that we use in the training, please complete of verify the following prerequisites
- complete the Desktop Installation. Be sure to include perl in the installation if you want to do training related to host-based test scripting and verify the diagnostics.
- install the development toolchain for your host, as described for linux or windows. This is required for building the STRIDE runtime and samples.
- read the STRIDE Overview article to familiarize yourself with the high-level approach and components of STRIDE.
What we train on
Our training articles are based on a handful of samples that we provide with the off-target framework. The samples are usually self-documented using doxygen and the contents will be attached to the test report whenever a sample is executed. What's more, these samples were created to be as simple as possible while still adequately demonstrating the topic at hand. In particular, the samples are very light on core application logic and tend to focus instead on the code required that leverages STRIDE to define and execute tests. The actual code under test in these samples is very minimal so as not to distract from the core test or instrumentation logic.
What you need to do
TBD
Need to review test reports
Need to review script / test code
Reminder that the wiki articles provide the technical content required to really understand the features
Need to review the “Examine the Results” sections that provide a summary of techniques / approaches
