...

• ''Attributes:'' order, description, timeout, async, ui, user defined

...

AfterClass

...

– Used to specify a static method within a TestCase should run once, after all of the tests in a given test case are complete. In other words, when all of the tests in a test case are complete, before proceeding to the next testcase, this method executes. Conversely to a BeforeClass method AfterClass should preform cleanup on created tables, disconnect from databases, etc. For more information about AfterClass see [Sequences]

• ''Attributes:'' order, description, timeout, async, ui, user defined

...

Before

...

– Used to specify a method with a TestCase should be run before every [Test] in that class. For more information about Before see [Sequences]

• ''Attributes:'' order, description, timeout, async, ui, user defined

...

After

...

– Used to specify a method with a TestCase should be run after every [Test] in that class. For more information about After see [Sequences]

...

– Used to define an advanced Before/After setup using an entire class allowing for increased reusability. For more information see [CreatingRules ]

• ''Attributes:'' order

...

Suite

...

– specifies that the class tagged is a Test Suite and will contain a list of public variables typed as the Test Cases or additional Test Suites you wish to run. This tag is commonly paired with the RunWith tag to know what runner to use on the tests within this class. (Note: The Suite tag by it self actually does nothing, and RunWith specified with the Suite runner is all you need to set to get a class to run as a suite.) For more information about test suites see [Terminology#Test_Suite ]

...

• ''Attributes:'' none, other than the fully qualified class name of the runner.

...

Ignore

...

– Can be used to ignore a specific Test or Theory, the test will still be built, but will be skipped over when running all tests in the TestCase. The test marked with this tag is still counted in the total tests count. For more information about Ignore see [Ignore]

• ''Attributes:'' description, user defined

...

Test

...

– Is used to specify that a method in a TestCase is a method you want FlexUnit to test. There are additional attributes that can be added to this tag such as (async) which is needed if the test is using asyncronous events or (expects="flash.errors.IOError") which indicates that you expect the Test to throw an exception of the specified type and it should catch it. For more information see user defined metadata

...

• ''Attributes:'' description, user defined, loader

...

Parameters

...

– Parameters allow for a multitude of values to be passed into a constructor of a TestCase. For more information about Parameterized testing seeParameterized Testing

...

• ''Attributes:'' description, user defined

Other tags:

...

ArrayElementType

...

– Used to define the associated object type contained with an Array, most specifically used with a static variable, or function, marked as a DataPoint. Keep in mind that this piece of metadata is not unique to FlexUnit 4, however is required by [ to function properly.

...