fixtup VS clirunner

I have written wait_port, the following function, for the open source library fixtup. fixtup starts containers so that a test can run. There is a need to wait before returning control or executing migration code until the container is operational. The wait_port helper allows you to wait in a hook before returning control to pytest.

Fixtup is an open source python library for testing a python application beyond code boundaries. It manages the creation of disposable environments and is compatible with all modern CI platforms that support docker-compose such as gitlab ci, github action, etc… The library works with pytest and unittest and runs on linux, macOS and windows.

I love Click for building Python command line interfaces (CLI). One useful feature Click provides is a CliRunner() helper class for testing. CliRunner invokes the script in an isolated environment allowing you to pass arguments, etc. Occasionally I work on projects that don't use Click. For example, if I want to provide a python3 -m packagename script that is ancillary to the primary use case and don't want to include Click as a dependency or want something that can be distributes as a stand-alone script without dependencies. In this case I'd usually use argparse. However, CLIs built with argparse (or old-fashioned manual sys.argv parsing) aren't nearly as easy to test. Thus I created clirunner which is a port of Click's test helper to work with non-Click apps. The API is compatible with Click's CliRunner so if you ever move a project to use Click, the tests should need little to no modification.