View Question

We have tests running with MSTest.exe via BuildMaster. As test file we specify dll that contains some unit tests. In the log we get the information that all tests pass and the following error message:

An unhandled exception occurred while executing this action: System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK__BuildTestResults'. Cannot insert duplicate key in object 'dbo.BuildTestResults'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Inedo.BuildMaster.Data.StandardDataFactory.ExecuteNonQuery(String storedProcName, DbParameter[] parameters) at Inedo.BuildMaster.Data.DataFactory.Inedo.Data.IDataFactory.ExecuteNonQuery(String storedProcName, DbParameter[] parameters) at Inedo.Data.WrappedStoredProc.ExecuteNonQuery() at Inedo.BuildMaster.Extensibility.Actions.Testing.UnitTestActionBase.Execute() at Inedo.BuildMaster.Extensibility.Actions.ActionBase.ParamlessExecute()

We also use MSTest action with other dlls in BuildMaster build plan and they execute with no errors.

Thanks

We have a known issue where if you have two test actions with the same group name in the same deployment plan, you will get this error.

The workaround is to use a different group name for each test action in the same plan.