With this EAP we introduce new feature for better test management in the project. Now, it is possible to mute test failures and if muted test fails in the subsequent build it won't affect build status.
This feature is useful if the test fails for some known reason, but it is currently not possible to fix it. For example, responsible developer is on vacation, or you are waiting for the system administrators to fix the environment. Or the test is failing intentionally, for example, if required functionality is not yet written (TDD). In these cases you can mute such failure and avoid unnecessary disturbance of other developers.
Note that muting of a test failure is dangerous operation, and we understand it. We want to add separate permission for this action, and grant this permission to Project Administrator role. So regular developers won't be able to mute test failures by default. Right now, there is no such permission, so be careful.
Also, at the moment the muted test can be unmuted manually only. In the next EAP we will add automatic unmute either by time, or when the test is fixed.
In the fields with icon, parameters completion now works. Just type % or click the icon, and choose required parameter from the list.
In TeamCity 6.0 you can reorder build steps, but with one significant limitation. If build configuration is inherited from a template, reordering is possible for the custom (not inherited) build steps only. And all custom build steps are placed after the inherited steps. It was impossible to insert build step between or before inherited step. Now this limitation is removed. In the inherited build configuration you can insert custom build steps at any place, before, between, or after the inherited steps, in any order. However, the order of inherited build steps can be changed in the template only.
Among BDD frameworks for .NET MSpec is probably the most popular. The official builds of MSpec are built using TeamCity. And now we have built-in MSpec runner designed specifically to run MSpec tests.
Note that coverage options are also available for MSpec tests.
Another good news for .NET developers is the availability of the new build feature: AssemblyInfo Patcher. In .NET world to set a build number to an assembly, you need to patch AssemblyInfo.cs files. This build feature simplifies this procedure. Just specify version format and the rest will be done automatically.
XML Report Processing functionality has been extracted to separate build feature. The advantage is that you can keep all XML Report settings in one place (in TeamCity 6.0 they were distributed among build steps).
Additionally this build feature has got support for Google Test reports.
Plugin now generates much less traffic when communicates with TeamCity server. This not only reduces load on the network, but also reduces CPU time on developer machine, required to process data. Moreover, while plugin is in collapsed state the traffic narrowed down even more.
Additionally, configuration parameters can now be changed for the remote run started from the IntelliJ IDEA plugin.