Description
I am wary about documenting a feature that encourages "out of design" use of the framework. However, I could see an option to change the default behavior by setting a global TableOutputFilter similar to the TestResultFormatter that already exists.
Each filter should be a procedure that will be called to "filter" the rows in the output based on its rules.
Something like:
tSQLt.TableOutputFilterAll @ResultTable NVARCHAR(MAX), @ResultColumn NVARCHAR(MAX), @ColumnList NVARCHAR(MAX)
tSQLt.TableOutputFilterDifferent @ResultTable NVARCHAR(MAX), @ResultColumn NVARCHAR(MAX), @ColumnList NVARCHAR(MAX)
tSQLt.TableOutputFilterTop @RowCount INT, @ResultTable NVARCHAR(MAX), @ResultColumn NVARCHAR(MAX), @ColumnList NVARCHAR(MAX)
@ColumnList might not be needed, but the interface should be the same across all of them, with additional required parameters (like @RowCount coming first.
If you take this on, we do need adequate test coverage to accept the PR.
Originally posted by @mbt1 in #35 (comment)