Comments
Sort by recent activity
Just spotted something...
I notice that your creating the actual and expected tables in the [dbo] schema. It is a better idea to create these tables in the same schema as the test suite.
But you are refencing them as if they are in the [BoardSummary] schema in your test:
INSERT INTO [BoardSummary].Expected
VALUES ( 90, 80, 80, 60, 60, 35 )
INSERT INTO [BoardSummary].Actual
( GreenUpper ,
GreenLower ,
AmberUpper ,
AmberLower ,
RedUpper ,
RedLower )
SELECT GreenUpper ,
GreenLower ,
AmberUpper ,
AmberLower ,
RedUpper ,
RedLower
FROM @Exec AS E
WHERE GroupedBy = 'TEST' / comments
Just spotted something...
I notice that your creating the actual and expected tables in the [dbo] schema. It is a better idea to create these tables in the same schema as the test suite.
But you a...
Yes this does still exist.
I blogged about it a while back Unit Testing Databases with tSQLt Part 6 – testing a SELECT stored procedure under the heading "Automatic Setup".
If that doesn't help, perhaps you could post your code. / comments
Yes this does still exist.
I blogged about it a while back Unit Testing Databases with tSQLt Part 6 – testing a SELECT stored procedure under the heading "Automatic Setup".
If that doesn't help, ...
An alternative view might be that if one uses cursors so rarely as to need a snippit to remeber all the correct syntax that's a good thing. / comments
An alternative view might be that if one uses cursors so rarely as to need a snippit to remeber all the correct syntax that's a good thing.