Today we've released v.2.11. It has some nice features and the major are:

Navigation flows
Already mentioned in previous post. It is a great help for novice users to become familiar with TargetProcess. Also it may works nicely as an alternative navigation.

Selenium and NUnit integration
Automated acceptance testing integration is a long awaited feature. Integration as usual implemented via plugins and it is really easy to add integration with any testing framework that may provide results in parseable format.

Getting Started area
Nothing to add. Contains useful information about TargetProcess usage.

Sample project generation
It is easier to learn the system when it has some real data. Now you may generate sample project and examine all reports, lists, etc.

Also with v.2.11 we are providing source code of all plugins under BSD license. You are free to modify and change them to fit your needs. They will be available for download next week.

More information about v.2.11

In the current iteration we are working on NUnit and Selenium integration. In fact it is almost completed. The integration implemented as a plugin. It is possible to configure profile for each project and in general the plugin is ready for continuous integration support.

The idea is very simple. CC server puts NUnit result file in some location, TargetProcess grabs it, parses it, creates new test plan run and sets passed/failed results for all test cases in this test plan. Thus you will have complete test cases run history without any manual actions.

The one potential problem is how to map Tests from NUnit or Selenium to Test Cases in TargetProcess. There will be several possible ways:

1. Test cases may have the same names as tests. For example, TheOnePlusTwo in NUnit and The One Plus Two in TargetProcess.
2. Tests may have test case ID as a part of the name. For example, TheOnePlusTwo_1876 test relates to test case with id 1876
3. It is possible to use the regular expressions to define the test name pattern. For example, TheOnePlusTwoTest in NUnit and The One Plus Two in TargetProcess.

You may wonder why we integrated with NUnit. The main reason is that Selenium has a nice Remote Control test tool. You write tests on your favorite language, for example C#, and run the tests using NUnit. We were looking for Selenium integration and NUnit integration is just a nice side-effect :)