Continuous mode

What scenario is the continuous mode trying to solve?

If you've used StatLight, and are doing some form of TDD, then your typical development steps probably look something like.
  1. Write Silverlight unit test
  2. Build project
  3. Execute StatLight against the test xap and see the test failure
  4. Write code to make test pass
  5. Build project
  6. Execute StatLight against the test xap and (hopefully) see the test pass

The above steps can get very tedious and are steps that, well, you just shouldn't have to do manually. This is where the continuous mode in StatLight will attempt to ease this pain a little.

What is the continuous mode?

The continuous mode is an option you can specify at the command line when running your first test against the xap. It will leave the application in a continuous monitoring mode. On first execution of StatLight it will run the unit tests and report to the console just at is usually does. However, StatLight will not exit, but instead sit in a monitoring mode, looking for a re-compilation (change in the test xap file). Once this change is detected, StatLight will automatcially kick off another test run.

So your workflow may now be something like:
  1. Write Silverlight unit test
  2. Build project
  3. Wait for results (or send random twitter message)
  4. Write code to make test pass
  5. Build project
  6. Wait for results (or another send random twitter message)

This option truly works best if you have a dual (or more) monitor setup. (You can place StatLight out of the way on one monitor, and write your Silverlight code in the other)

Command line args for continuous mode:
-c, --Continuous           Runs a single test run, and then monitors the
                               xap for build changes and re-runs the tests
                               automatically.

Last edited Feb 25, 2010 at 3:53 PM by staxmanade, version 1

Comments

No comments yet.