tSQLt.AssertEqualsTable should allow for pattern matching on strings and precision on float columns

[lizbaron]

This is a discussion item. Is this valuable? If so, how should this be implemented?

One option would be to add a "tag" to the column name in the expected table. Another option would be to add a column_handler extension framework. The latter would allow for flexible XML comparisons.

Please comment on this issue with your ideas or thoughts.

[lizbaron]

Here is something of a workaround that we used in one of the tSQLt tests:

  SELECT _id_, CleanUpCmd INTO #Actual FROM tSQLt.Private_CleanUpCmdHandler_SpyProcedureLog;
  SELECT TOP(0) A._id_, A.CleanUpCmd AS [%CleanUpCmd] INTO #Expected FROM #Actual A RIGHT JOIN #Actual X ON 1=0;
  INSERT INTO #Expected VALUES(1,'%tSQLt.Private_NoTransactionHandleTables%'),(2,'%tSQLt.UndoTestDoubles%');

  SELECT * INTO #Compare
    FROM(
      SELECT '>' _R_,* FROM #Actual AS A WHERE NOT EXISTS(SELECT 1 FROM #Expected E WHERE A._id_ = E._id_ AND A.CleanUpCmd LIKE E.[%CleanUpCmd])
       UNION ALL
      SELECT '<' _R_,* FROM #Expected AS E WHERE NOT EXISTS(SELECT 1 FROM #Actual A WHERE A._id_ = E._id_ AND A.CleanUpCmd LIKE E.[%CleanUpCmd])
    )X
  EXEC tSQLt.AssertEmptyTable @TableName = '#Compare';