Versions Compared

Old Version 1

changes.mady.by.user Erik de Bruin

Saved on

compared with

New Version 2

changes.mady.by.user Tom Chiverton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Copy Erik's announcement email into the intro and format it

Introduction

There is SDK wide support for FlexUnit tests, and each project maintains it's own set of tests.

  1. The main build script has a target 'test'; this target is not part of the 'main' run and does nothing but call:
  2. The frameworks build script's 'test' target, which cleans the previous test reports and calls any test targets ('xxx-test') that may exist, which in turn call
  3. The project build script's 'test' target, that sets up the project specific properties and calls back to
  4. 'flexunit-tests.xml' in the SDK root.
    This file is where the magic happens. Based on the input from the project build script, it runs any FlexUnit tests that have been set up for that project and reports back success or fail.

Any projects for which we want to add FlexUnit tests can easily hook into this system by adding the tests and add a copy of the 'test' target to their build script.

Add tests to SDK project

xxx

...