Setting up your CI Environment

From STRIDE Wiki
Revision as of 16:58, 14 September 2009 by Timd (talk | contribs) (Created page with 'To reap the maximum benefit from your test assets, you need to run your tests as part of a [http://en.wikipedia.org/wiki/Continuous_integration continuous integration] environmen…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

To reap the maximum benefit from your test assets, you need to run your tests as part of a continuous integration environment.

In this scenario, the following automated steps take place on a regular, periodic basis (typically nightly):

  • Automated source code check out from source control system
  • Automated build of the target executable code (including STRIDE runtime and tests)
  • Automated downloaded of executable image to the target hardware
  • Automated start of target code execution on the hardware
  • Automated running of all STRIDE tests and results publication to Test Space

Note that the Test Space to which the results are published should be configured to notify on setbacks and errors.