Last Updated: 31 Jul 2020 08:19 by ADMIN
Created on: 24 Jul 2020 12:26
Type: Feature Request
Change In Dev status from project setting to Test property

When multiple users have their hands on a product and code (10+ in our case) having to consistently address conflict issues with settings files has become overwhelming.  I question why the "In Development" property is maintained at the project settings instead of maintaining the at the individual test level will significantly reduce issues with maintaining what is actually in development.

1 comment
Posted on: 31 Jul 2020 08:19

Hi David,

The TFS integration in Test Studio has no built-in mechanism for resolving conflicts. Thus, when multiple people are working on the same project and indirectly on the same files (like the Settings.aiis file, for example), they often face the need to resolve such conflicts. 

As you noted, one of the indirect changes applied in the Settings file of a Test Studio project is when a test is set to "In Development" state. The main idea of this property is to exclude this test from the project compilation process and this is why it is set on project instead of single test level. 

Still the idea to change how this property is set and help in reducing the conflicts to resolve in a team work mode, can be considered as a feature request in our backlog and I submitted this internally. This is the public item, which progress you can follow in the future. 

Thank you for your understanding in advance.

Progress Telerik