playtest2
Table of Contents
Installation
Prerequisites
Setting up Gauge with playtest2
- Install
playtest2as a uv tool:
$ uv tool install playtest2
This provides the playtest2 setup command from an isolated environment outside your E2E test project.
- Create a virtual environment for your E2E test project:
$ cd /path/to/e2e/project
$ python -m venv .venv --upgrade-deps
$ source .venv/bin/activate
- Install
playtest2in the E2E virtual environment too:
(.venv) $ python -m pip install playtest2
The uv tool installation is used for generating Gauge configuration. The E2E virtual environment installation is used when Gauge runs the Python steps.
Usage
Gauge Configuration
- From the E2E test project root, run the uv tool-installed
playtest2 setupto createpython.propertiesinenv/default/.
$ playtest2 setup
# If you have own step implementation directories
$ playtest2 setup your_step_impl1 your_step_impl2
[!TIP] Generated env/default/python.properties example
STEP_IMPL_DIR = /**absolute**/path/of/uv/tool/environment/lib/python3.x/site-packages/playtest2,your_step_impl1,your_step_impl2
[!IMPORTANT] Run
playtest2 setupusing the uv tool-installed command, not the command inside your E2E project's.venv. This keepssite-packages/playtest2outside the E2E project directory and avoids Gauge Python loader issues with project-local.venvpaths.
- Create
playtest2.propertiesinenv/default/.
SUT_BASE_URL = http://127.0.0.1:8000
Run gauge command in your E2E test project:
(.venv) $ gauge run specs
Spec example
# サンプルアプリのテスト
## GETリクエストが送れる
* パス"/"に
* メソッド"GET"で
* リクエストを送る
* レスポンスのボディが
* JSONのパス"$.message"に対応する値が
* 文字列の"Hello World"である
Development
Prerequisites: Hatch (Installation)
Lint
hatch fmt && hatch run types:check
Test
hatch test --randomize --doctest-modules
License
playtest2 is distributed under the terms of the MIT license.
Metadata
Release files for playtest2 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| playtest2-0.0.7.tar.gz | 9.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| playtest2-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.5 kB
Release files / playtest2-0.0.7.tar.gz
| Download URL | playtest2-0.0.7.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b88feaf4ea25b031ae1fe3eb0b4f937156eb5369c6f58cd4676bd3c3eaff2893
|
|
BLAKE2b-256 checksum How to use checksums |
5d8a5131dfa6ca33eda75033d33800b36fcf5a49648fa093b5f7c00d4340c650
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.
Transparency logRelease files / playtest2-0.0.7-py3-none-any.whl
| Download URL | playtest2-0.0.7-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d799dde79a19d4e5fdc9607e051d63b315a3ec8e47729e55321bf2b641edb68
|
|
BLAKE2b-256 checksum How to use checksums |
5fb6ca3cefe05e45facdf81d3c1a618f22810469f3d7043f5fae7ec464c43af3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.
Transparency log