Bug Fixes:
- When using tSQLt.Run or tSQLt.RunTestClass, if an object name on the dbo schema had the same name as a test class, the test class could not be executed.
- If the output of an AssertTableEquals or the length of a test case name was too long, an error was be produced.
New Features:
- A new procedure, tSQLt.NewConnection, was added which allows statements to be executed synchronously in a different connection context.