Skip to content

Background

BrianGenisio edited this page Apr 4, 2011 · 6 revisions

Why Another Flex Based Testing Framework?

As of today, there is a great testing framework for Flex: FlexUnit. Why Jasmine?

Jasmine for Javascript has a particular reason for being. But why port it to Flex? Why might you want to use Jasmine-Flex?

Behavior-Driven Development (BDD) is the next step in the evolution from Test-Driven Development (TDD). It supports the idea of testing behavior, not just inputs and outputs. It allows you to organize your tests in a context-level hierarchy that feels more natural to the BDD workflow.

Jasmine was designed with a few principles in mind. We believe that a good JavaScript/ActionScript testing framework (excerpts from the Jasmine-js project):

  • should not be tied to any browser, framework, platform, or host language.
  • should have idiomatic and unsurprising syntax.
  • shouldn't intrude in your application's territory (e.g. by cluttering the global namespace).
  • should play well with IDEs (e.g. test code should pass static analysis).

Some of our goals while writing Jasmine:

  • it should encourage good testing practices.
  • it should integrate easily with continuous build systems.
  • it should be simple to get started with.

The result is Jasmine, and we love test-driving our code with it. Enjoy.

Clone this wiki locally