flexunit4

Is it OK to have multiple assertions in a unit test when testing complex behavior?

Here is my specific scenario. I have a class QueryQueue that wraps the QueryTask class within the ArcGIS API for Flex. This enables me to easily queue up multiple query tasks for execution. Calling QueryQueue.execute() iterate through all the tasks in my queue and call their execute method. When all

Is it OK to have multiple assertions in a unit test when testing complex behavior?

Here is my specific scenario. I have a class QueryQueue that wraps the QueryTask class within the ArcGIS API for Flex. This enables me to easily queue up multiple query tasks for execution. Calling QueryQueue.execute() iterate through all the tasks in my queue and call their execute method. When all

Jenkins CI server setup for Adobe AIR app (With FlexUnit4 and GitHub as repo)

I have an Adobe AIR app written with Robotlegs 1.5.2. The unit test framework used is FlexUnit4. I already have a Jenkins CI setup for projects written with CakePHP 2.x and unit test framework of PHPUnit. My Jenkins CI server is on Ubuntu 11.10 on Rackspace. I intend to use the same Jenkins server

Is it OK to have multiple assertions in a unit test when testing complex behavior?

Here is my specific scenario. I have a class QueryQueue that wraps the QueryTask class within the ArcGIS API for Flex. This enables me to easily queue up multiple query tasks for execution. Calling QueryQueue.execute() iterate through all the tasks in my queue and call their execute method. When all