Testing with libtmux

The pytest plugin supplies server and session fixtures. A session fixture also creates its server. Use fsession_params for fixture setup options. For a standalone program, the complete capture example uses an explicit private socket and finally cleanup.

Run a complete example¶

Capture pane output includes a complete Python executable, imports, dependency setup and cleanup. Its output check fails when the expected line does not arrive before the deadline. Start with that program when adapting the pattern to your own test runner.

Keep server ownership explicit¶

Give each test a private socket and a known tmux configuration. Stop the server the test creates, including when startup or an assertion fails. Preserve the original failure and report cleanup errors so a leaked server remains visible.

A connection to an existing server has a different lifetime. The attach program leaves that server running and lets its launcher own cleanup.

Wait for the state you assert¶

Wait for the actual output or completion condition with a deadline. Sending keys returning successfully does not establish that the application finished. Capturing output explains the difference between a screen snapshot and a stream of output.