FlexMonkey brings unit testing to Flex user interface developers
In Stu Stern’s recent InfoQ.com article on UI testing and FlexMonkey, he explains the code-a-little-test-a-little (CALTAL) approach to test driven development with user interface development and walks you through using FlexMonkey to support the theory.
The practice of maintaining automated unit test suites has gained widespread acceptance over the past decade to the point where most developers today either engage in some amount of test writing or at least feel bad for not doing it. This rise in automated unit testing has led to some confusion about who should be testing what. Should developers strive for 100% code coverage with their unit tests, and if so, does that mean we no longer need dedicated QA testers? Many development teams draw the line at the user interface, reasoning that since user interfaces can be exercised with little or no programming they can be tested more economically by dedicated testers, either manually or with specialized testing tools. This division of labor has led many to divide the world of testing into “unit testing” and “functional testing”, with developers providing the former and QA testers providing the latter. In this article we’ll explore how Gorilla Logic’s new, open source Flex user interface automation testing tool, FlexMonkey, can enhance the productivity of both developers and QA testers. FlexMonkey allows developers to incorporate user interface testing into unit test suites and continuous integration environments, and allows QA testers to expand those unit tests to create and maintain comprehensive quality tests.
Enjoy the full article at: http://www.infoq.com/articles/flexmonkey-ui-unit-testing
