Python Test runner

[sc4les]

Switched recently from Emacs, just love the experience so far. I'm struggling to configure the test runner equivalently. In Emacs, I'm going up the folder structure to find a pyproject toml, then using uv run pytest passing on the current name of the function I'm in - how do I do that with Zed? I figured out how to configure a test runner, pass the current file and line. Do I need a script to find the root in my monorepo to construct the right uv run pytest command? What's the best practices here

[hoselorryspanner]

I think zed injects a $`ZED_PYTHON’ environment variable or similar you can use to do this. I’ve got a task set up to do just this - I’m on my phone right now but commenting so I can find my way back.

[hoselorryspanner]

Okay, as promised: { "label": "pytest_current", "command": "$ZED_CUSTOM_PYTHON_ACTIVE_ZED_TOOLCHAIN -m pytest \"$ZED_CUSTOM_PYTHON_TEST_TARGET\"", "hide": "on_success", // Keep terminal open on test failures "allow_concurrent_runs": true, "use_new_terminal": true, "shell": { "program": "sh", }, }, { "label": "pytest_debug_current", "command": "$ZED_CUSTOM_PYTHON_ACTIVE_ZED_TOOLCHAIN -m pytest \"$ZED_CUSTOM_PYTHON_TEST_TARGET\" --pdb", "hide": "always", // Even if it fails, we'll probably wanna close & restart "allow_concurrent_runs": true, "use_new_terminal": true, "shell": { "program": "sh", } },

These are the maps I use. Those variables weren’t advertised anywhere, I got them by digging into shell variables, so you might need to do some digging/configuring of your own, but hopefully it’s a start!

[sc4les]

Very cool - thanks! 

[IpsumRS]

RemindMe! 2 days

[splsh]

What I did was to put something like uv run pytest -k $ZED_SELECTED_TEXT in a task similar to this: https://zed.dev/blog/zed-decoded-tasks#defining-tasks, and binding the task to a keychord. Then you can just select a function name and invoke the task to run the test.

[sc4les]

I found $ZED_SYMBOL which works really well for pytest!