Improve debuggability in event of test failure

pytest with code coverage enabled won’t provide useful contextual information provided normally by pytest. This makes debugging failures especially difficult.

As an example: with code coverage enabled I may see the following failure:

        try:
            list(client.execute_query(create_stored_proc))
            row_counts = []
            for rows, _, _, _, is_error in client.execute_query(exec_stored_proc):
                row_counts.append(len(rows))
>           assert row_counts[0] != 2
E           assert 2 != 2

tests/test_mssqlcliclient.py:190: AssertionError

But if I run the same test without coverage reports (normal pytest call) I get a lot of great info for debugging:

        try:
            list(client.execute_query(create_stored_proc))
            row_counts = []
            for rows, _, _, _, is_error in client.execute_query(exec_stored_proc):
                row_counts.append(len(rows))
>           assert row_counts[0] != 2
E           assert 2 != 2

_          = 'EXEC sp_mssqlcli_multiple_results'
client     = <mssqlcli.mssqlcliclient.MssqlCliClient object at 0x102ff6d90>
create_stored_proc = "CREATE PROC sp_mssqlcli_multiple_results AS BEGIN SELECT 'Morning' as [Name] UNION ALL select 'Evening' SELECT 'Dawn' as [Name] UNION ALL select 'Dusk' UNION ALL select 'Midnight' END"
del_stored_proc = 'DROP PROCEDURE sp_mssqlcli_multiple_results'
exec_stored_proc = 'EXEC sp_mssqlcli_multiple_results'
is_error   = False
row_counts = [2, 3]
rows       = [['Dawn'], ['Dusk'], ['Midnight']]

tests/test_mssqlcliclient.py:190: AssertionError

Is there any way I can get a stack trace similar to the below example?

[blueyed]

-l? Not sure what that does, pretty sure I’m not using it.

Looking at pytest --help can be useful in general… 😃

[blueyed]

-l shows locals:

_          = 'EXEC sp_mssqlcli_multiple_results'
…
rows       = [['Dawn'], ['Dusk'], ['Midnight']]

With my branch/fork above it shows options used via addopts ini setting or PYTEST_ADDOPTS.