Add new assertions tSQLt.AssertIsNull, tSQLt.AssertNotNull

[bartread]

These would be used for testing whether or not, for example, some variable has a value. E.g.:

EXEC @insertedAddressId = [someschema].[SomeStoredProcedure] ...
EXEC tSQLt.AssertNotNull
    @Value = @insertedAddressId
    @Messsage = N'Should have returned a non-null ID for INSERTed address.'

tSQLt.AssertIsNull would have similar syntax and usage.

[mbt1]

This is on the backlog already. For now, you can use tSQLt.AssertEquals and tSQLt.AssertNotEquals to achieve the same thing.

However, I question the usefulness of your example test. Instead of asserting that any value is returned, you should assert that the correct value is returned. You could for example do this: Fake the table and then insert a row. You will end up with a single row in that table. Its ID should match the returned value.