Page History

...

• Any methods that contain a medadata tag of [BeforeClass] are executed.

• Wiki Markup
  Once the [\[BeforeClass\]|FlexUnit BeforeClass] methods have finished, each method labeled as

  [

  \[Test\]

  ]

  is sequenced with all methods that contain [\[Before\]|FlexClient Before] and [\[After\]|FlexClient After] and variables with [\[Rule\]|FlexClient Rule] metadata tags Before each test, all class variables marked as [\[Rule\]|FlexClient Rule] will be executed followed by all methods marked as a [\[Before\]|FlexClient Before] method. After this occurs, the actual test method will execute. After the test has finished, regardless of whether it succeeded or failed, all class variables marked as [\[Rule\]|FlexClient Rule] will execute followed by all methods marked as an [\[After\]|FlexClient After] method. This procedure will be repeated for all tests in the class.

• Any methods that contain a metadata tag of [AfterClass] are finally executed.

...

Before any before class, after class, before, after, rule or test methods are executed, they are decorated in order to add functionality. These decorations are used to wrap the invocation of a method with code that should be executed before or after the method in a synchronous nature. Each decorator is applied to the method if necessary; if it is not needed, the decorator is not applied.

FlexClient Runners and BuildersBack