菜单
Run the integration tests (Docker / pip / subprocess-based) — invoke when verifying a change that touches session launching, packaging, or subprocess handling, since these tests are excluded from the default run. Encodes the required -s flag and the other gotchas that cause silent failures
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/deephaven/deephaven-mcp --skill integration-tests-run命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | integration-tests-run |
| description | Run the integration tests (Docker / pip / subprocess-based) — invoke when verifying a change that touches session launching, packaging, or subprocess handling, since these tests are excluded from the default run. Encodes the required -s flag and the other gotchas that cause silent failures |
Integration tests are marked @pytest.mark.integration and are excluded by default in pyproject.toml's addopts (-m 'not integration').
uv run pytest -m integration -s
-m integration — selects integration tests (deselected by default).-s — disables pytest's stdout/stderr capture. Required. Pytest's capture mechanism interferes with asyncio.subprocess.PIPE; the Deephaven JVM detects the broken pipe and aborts with Aborted!. The failure mode is non-obvious: the pip integration test will pass in isolation and fail when run after Docker tests under capture.uv run pytest tests/path/to/test_<file>_integration.py -s (the -m integration selector is implied by file content but the -s flag is still required).test_<file>_integration.py (see ref-python-coding-practices rule 5).tests-run and tests-run-file.