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 :)

We are finalizing TP 2.2 implementation and one feature is Test Cases Library. Test Cases library contains general test cases that can be reused in different projects. For example, login functionality is almost the same in all projects as well as login testing. So you may create several test cases for "login user" feature and save them in test case library. Then you may select test cases and copy them into another project. Quite useful stuff.

However, one problem is test cases categorization. You may have 1000+ test cases in library and it is not so simple to find required test cases to copy. There are several options:

1. Add Category property for test case and allow users to add/delete categories. Likely there will be QA lead who manage categories. So people will often ask him "please, add category XYZ".
2. Allow users to describe test cases in free form using tags (so-called folksonomy).

We've decided that solution 2 is more natural and flexible option.

The only problem with tags is that there will be lot of them. So you have to a) highlight tags with high rank and b) provide a way to filter tags. Tags highlighting with font size is a common and good way to show the most frequent tags, while filtering is less common feature. We've implemented tags filter this way. For example, user types "a" and sees only tags that starts on "a", user types "ag" and sees tags starts on "ag" and so on. It is just a lookup filter.

If tags concept will be proven for test cases library we are going to spread it on user stories, bugs and all important content in TargetProcess.

On Friday we’ve started Test Cases module development. It will have some nice new features that where requested by many people. First of all, there will be test cases library – general test cases storage. It will be possible to copy test cases from library to project and vise versa. Usefulness of test cases library is obvious. For example, almost all web applications have login form and authentication mechanism. Test cases for such functionality are almost the same, so it is natural to create them once and use for all relevant projects.

The second highly requested feature is ability to assign the same test case to several test plans. It was not possible in TP 1.7, but will be added into TP 2.1. The reason is that often you need to have two test plans for one feature: one is smoke test plan and second full test plan for example. So you have to assign the same test case to both test plans.

Some additions will be made to enable time tracking for test plans execution and we’ll likely improve Test Runner to make it more usable. Other features will be almost the same as in TP 1.7 since people really liked how test cases module works.