The presentation gives a comparative analysis of various mocking frameworks available to help writing unit tests in Actionscript/Flex

1. Mocking in ActionScript 3.0: Comparative Analysis of various mocking frameworks

3. What is Mocking? What is Mock Object?

4. mock objects are simulated objects that mimic the behavior of complex, real objects in controlled ways

5. Why to Mock? When to Mock? Mock == Actual Object?

6. If an object has any of the following characteristics, it may be useful to use a mock object in its place: - supplies non-deterministic results (e.g. the current time or the current temperature); - has states that are difficult to create or reproduce (e.g. a network error ); - is slow (e.g. a complete database, which would have to be initialized before the test); - does not yet exist or may change behavior; - would have to include information and methods exclusively for testing purposes (and not for its actual task).

7. How to mock?

8. Example: The Greeting component says Hello in any language. Greeting uses a Translator component to translate “Hello” from English to the selected language. ITranslator is an interface containing the translate method – parameters from, to and word, which returns the translated word;

9. Traditional Way Vs Mocking Frameworks

10. Traditional Way

11. Evolution of Mocking Frameworks Mock4AS MockAS3 Mockolate

14. FlexUnit: Runners & Rules Runners are classes that implement IRunner, and have the capability to run specific types of suites, tests, or methods. Rules are an advanced concept whose basic functionality is similar to the [Before] and [After] concepts, allowing for reusable, dynamic classes that will execute functionality before and after each test.

18. What Suites You??

19. Questions??