cli-test-helpers 1.0.0

Functional tests

Start with a simple set of functional tests:

• Is the entrypoint script installed? (tests the configuration in your setup.py)

• Can this package be run as a Python module? (i.e. without having to be installed)

• Is command XYZ available? etc. Cover your entire CLI usage here!

This is almost a stupid exercise: Run the command as a shell command and inspect the status code of the exiting process (see example). The trick is that you run a non-destructive command, e.g. by using the usual --help option of every command. This should cover your entire CLI user interface definition.

Unit tests

Then you’re ready to take advantage of our helpers.

ArgvContext allows you to mimic the use of specific CLI arguments:

def test_cli_command(mock_command):
    """Is the correct code called when invoked via the CLI?"""
    with ArgvContext('foobar', 'baz'):
        foobar.command.baz()

    assert mock_command.call_count == 1

EnvironContext allows you to mimic the presence of environment values:

def test_fail_without_secret():
    """Must fail without a ``SECRET`` environment variable specified"""
    message = "Environment value SECRET not set."

    with EnvironContext(SECRET=None):
        with pytest.raises(SystemExit, match=message):
            foobar.command.baz()
            pytest.fail("CLI doesn't abort with missing SECRET")

See example.

TDD

Remember to stick to the test-driven mantra:

1. Write one line of test code. Make the test fail.

2. Write one line of application code. Make the test pass.

3. Goto 1.