You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is almost certainly down to suitable test data not being generated reliably, rather than a problem with the code being tested.
Rethink how it's done - a test suite should update the data, run tests on it, then roll back the transaction, using the same database as other tests, rather than creating a separate database.
On line 140 of SqlServerStatisticsMaxResultsDataSourceFixture the sixth bowler had no overs with runs conceded, and that threw an exception. That made both tests fail because the fixture was unavailable.
The text was updated successfully, but these errors were encountered:
This is almost certainly down to suitable test data not being generated reliably, rather than a problem with the code being tested.
Rethink how it's done - a test suite should update the data, run tests on it, then roll back the transaction, using the same database as other tests, rather than creating a separate database.
On line 140 of SqlServerStatisticsMaxResultsDataSourceFixture the sixth bowler had no overs with runs conceded, and that threw an exception. That made both tests fail because the fixture was unavailable.
The text was updated successfully, but these errors were encountered: