revitdevtool-pytest 0.0.3__tar.gz → 0.2.0__tar.gz

{revitdevtool_pytest-0.0.3 → revitdevtool_pytest-0.2.0}/.gitignore

@@ -14,3 +14,5 @@ build/
 .env
 .venv/
 venv/
+.idea/
+.gitnexus

{revitdevtool_pytest-0.0.3 → revitdevtool_pytest-0.2.0}/.vscode/settings.json

@@ -22,10 +22,4 @@
     "basedpyright.importStrategy": "useBundled",
     "basedpyright.analysis.typeCheckingMode": "off",
     "python.testing.pytestEnabled": true,
-    "python.testing.pytestArgs": [
-        "--revit-launch",
-        "--revit-version=2025",
-        "--revit-launch-timeout=180",
-        "tests"
-    ]
 }

revitdevtool_pytest-0.2.0/AGENTS.md

@@ -0,0 +1,112 @@
+# AGENTS
+
+## Overview
+
+This is the pytest client plugin for RevitDevTool. It bridges local pytest with a live Revit process via Named Pipe JSON-RPC.
+
+## Architecture
+
+```
+Local pytest (collect) → Named Pipe → Revit process (PytestRunner.py) → Results → Local pytest (report)
+```
+
+### Module Map
+
+| Module | Role |
+|--------|------|
+| `plugin.py` | Hook orchestrator — lifecycle, options, bridge setup |
+| `connection.py` | Bridge lifecycle — discover, connect, lease, launch |
+| `bridge.py` | Wire protocol — Named Pipe framing, request/response |
+| `discovery.py` | Pipe scan, Revit registry lookup, process launch |
+| `reporting.py` | Map remote CaseResult → pytest TestReport |
+| `suite_leasing.py` | Cross-process Revit instance allocation (file-based) |
+| `suite_lock.py` | Windows mutex for same-suite concurrency guard |
+| `dialog_resolver.py` | Auto-dismiss Revit startup dialogs via Win32 |
+| `models.py` | Wire protocol data models (mirrors C# PytestContracts) |
+| `constants.py` | Shared constants, option names, defaults |
+
+### Revit-Side (in RevitDevTool repo)
+
+| File | Role |
+|------|------|
+| `PytestRunner.py` | Embedded script — runs `pytest.main()` inside Revit |
+| `SetupRevit.py` | Runtime setup — API refs, I/O redirection |
+| `PytestExecutionService.cs` | C# orchestrator — receives pipe request, invokes Python |
+| `PytestContracts.cs` | C# wire models (mirrors `models.py`) |
+
+## Key Design Decisions
+
+- **Dual pytest model**: Local pytest collects tests; remote pytest executes them. This enables IDE integration (test tree, navigation) while executing in Revit's thread.
+- **`--capture=sys`**: Required because fd-level capture (`os.dup2`) doesn't work in embedded Python.NET.
+- **`--disable-plugin-autoload`**: Prevents third-party plugins from interfering with in-Revit execution.
+- **`sys.__pytest_running__`**: Flag set by PytestRunner to prevent SetupRevit from hijacking stdout/stderr during test runs.
+- **Streaming vs batch**: CLI gets real-time progress notifications; IDE adapters get one batch to avoid double-counting.
+- **Suite leasing**: File-based lease store binds suite → Revit PID across processes. Mutex prevents same-suite parallel runs.
+- **force_launch**: When enabled, spawns new Revit and waits for its exact PID pipe (ignores existing instances).
+
+## Running Tests
+
+```bash
+# From project root with .venv activated:
+pytest
+
+# Or via uv / pixi:
+uv run pytest
+pixi run pytest
+
+# Specific test:
+pytest tests/test_active_state.py::test_active_view_info -v
+```
+
+Plugin auto-enables `-rP` (show captured stdout for passing tests).
+
+## Configuration
+
+All options in `pyproject.toml` under `[tool.pytest.ini_options]`:
+
+```toml
+revit_version = "2025"        # Required for launch
+revit_launch = false           # true = always spawn new instance
+revit_timeout = "60"           # Per-test timeout (seconds)
+revit_launch_timeout = "180"   # Startup wait (seconds)
+revit_pipe = ""                # Explicit pipe (bypass discovery)
+```
+
+## Fixtures Pattern
+
+```python
+# conftest.py
+@pytest.fixture(scope="session")
+def revit_uiapp():
+    return __revit__  # UIApplication injected by host
+
+@pytest.fixture(scope="session")
+def revit_doc(revit_uiapp):
+    return revit_uiapp.ActiveUIDocument.Document
+
+@pytest.fixture
+def revit_auto_rollback(revit_transaction_service):
+    """Start undo tracking, revert after test."""
+    revit_transaction_service.StartChanges()
+    try:
+        yield revit_transaction_service
+    finally:
+        revit_transaction_service.RevertChanges()
+```
+
+## Common Traps
+
+- Tests execute **inside Revit**, not locally. `import` statements for Revit API (`Autodesk.Revit.DB`) only work at test runtime.
+- `__revit__` is a builtin injected by SetupRevit — always access via fixtures, not direct import.
+- Revit API requires main-thread access. All tests run sequentially via FIFO queue (`IHostContextExecutor`).
+- Named Pipe format: `Revit_{year}_{pid}` (e.g. `Revit_2025_12345`).
+- PEP 723 dependencies in `conftest.py` are auto-installed by `PytestDependencyService` before execution.
+- `force_launch` requires `revit_version` to be set — otherwise exits with config error.
+- Print output inside tests is captured by pytest's `--capture=sys` mechanism and returned via `CaseResult.stdout`.
+
+## Change Rules
+
+- Wire protocol changes must update both `models.py` (Python) and `PytestContracts.cs` (C#).
+- Adding CLI options: register in both `pytest_addoption` (CLI) and `parser.addini` (INI).
+- Connection logic is stateless by design — all functions receive parameters, no module-level mutable state except `plugin.py` globals.
+- After modifying connection/discovery logic, manually test with both `revit_launch = true` and `false`.

revitdevtool_pytest-0.2.0/CHANGELOG.md

@@ -0,0 +1,115 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [0.2.0] - 2026-05-31
+
+### Added
+
+- **Auto print capture:** plugin automatically enables `-rP` behavior — captured `print()` output is shown for both passing and failing tests without any user configuration.
+- **PID-aware pipe discovery:** `wait_for_revit_pipe` can now wait for a specific process ID, ensuring `force_launch` connects to the newly spawned instance only.
+
+### Changed
+
+- **`revit_launch` → force_launch semantics:** renamed internal parameter from `prefer_fresh` to `force_launch`. When enabled, the plugin disconnects any existing bridge, spawns a new Revit instance, and waits for that exact PID's pipe — never reuses existing instances.
+- **`_opt_bool` fix:** corrected boolean option parsing so `revit_launch = true` in `pyproject.toml` is properly respected when no CLI flag is explicitly passed.
+- **Type annotations refactor:** resolved false-positive IDE warnings across `bridge.py`, `connection.py`, `suite_leasing.py`, and `dialog_resolver.py`.
+- **`SetupRevit.py` (Revit-side):** I/O hijacking is now conditional on `sys.__pytest_running__` flag — prevents conflict with pytest capture during test execution.
+- **`PytestRunner.py` (Revit-side):** sets `sys.__pytest_running__ = True` during execution; top-level error handling wraps entire `_run()` to always return structured JSON.
+
+### Removed
+
+- **`discover_tests()`** method from `bridge.py` (client-side dead code; server endpoint remains).
+- **`DiscoverRequest` / `DiscoverResponse`** classes from `models.py` (unused by client).
+- **`BRIDGE_METHOD_TESTS_DISCOVER`** constant (no longer referenced).
+- **`resolve_existing()` / `get_suite_process_id()` / `_prune_stale()`** from `suite_leasing.py` (unused).
+- **`launch_revit()`** from `discovery.py` (replaced by `start_revit` + PID tracking).
+- **`addopts = "-rP"`** from `pyproject.toml` (now automatic via plugin).
+
+### Fixed
+
+- **`revit_launch = true` in INI ignored:** `_opt_bool` now correctly reads INI value when CLI flag is not explicitly set.
+
+## [0.1.0] - 2026-05-03
+
+### Added
+
+- **Real-time streaming:** test progress notifications streamed from Revit to the pytest client during execution.
+- **Suite leasing:** Windows Mutex-based exclusive access prevents multiple pytest processes from connecting to the same Revit instance.
+- **Test discovery:** `PytestRunRequest` + `_BridgePlugin` integration enables `--collect-only` discovery without executing tests.
+- **Reporting module:** remote `CaseResult[]` mapping back to pytest `TestReport`, with `run_remote_session` orchestrating discover + run.
+- **Connection module:** centralized `ensure_bridge()` with auto-connect, lease management, and Revit auto-launch flow.
+- **Schedule API tests:** comprehensive test suite for Revit schedule operations (copy, field mapping, header, template, custom workflow).
+- **Image export tests:** `test_image_export.py` covering `RevitImageExporter`.
+- **Document & transaction tests:** `test_revit_document.py`, `test_revit_transactions.py`.
+- **Session cleanliness tests:** `test_session_cleanliness.py`, `test_active_state.py` verifying state isolation between runs.
+- **Streaming tests:** `test_streaming.py` validating progress notification flow.
+- **Dependencies tests:** `test_dependencies.py` verifying package resolution.
+- **GitNexus integration:** AGENTS.md, CLAUDE.md, and CLI skills for graph-based code intelligence.
+- **Project setup guide:** recommended `uv` and `pixi` workflows in README.
+
+### Changed
+
+- **Architecture rewrite:** `plugin.py` restructured — execution now intercepted via `pytest_runtestloop` instead of `pytest_pyfunc_call`. Remote session orchestrates discover + run in a single round-trip.
+- **Configuration:** primary config via `[tool.pytest.ini_options]` in `pyproject.toml` — CLI flags remain as overrides.
+- **`bridge.py`:** expanded with `discover_tests()`, `run_tests()`, notification dispatch, frame protocol hardening.
+- **`models.py`:** new `DiscoverRequest`, `RunRequest`, `RunResponse`, `CaseResult`, `CollectionError` contracts.
+- **`constants.py`:** centralized all bridge methods, option names, timeouts, pipe patterns.
+- **`pyproject.toml`:** bumped `revit_launch_timeout` to 180s, added `revit_timeout` default.
+
+### Removed
+
+- **`serializer.py`:** deprecated — test code serialization replaced by structured discovery + run flow.
+- **`.vscode/settings.json`:** removed from repo; config lives in `pyproject.toml`.
+
+### Notes
+
+- `0.1.0` represents a major architectural shift from single-test relay to session-oriented orchestration. The plugin now discovers tests remotely, runs them in batch, and streams progress back in real-time.
+- Suite leasing ensures safe concurrent usage across multiple test suits targeting the same Revit year.
+
+## [0.0.3] - 2026-04-10
+
+### Fixed
+
+- Fixed Revit auto-launch dialog handling by starting the startup dialog resolver immediately after spawning Revit, before waiting for the named pipe.
+- Fixed startup dialog button selection to prefer safe allow-list actions such as `Always Load` and `Load Once`.
+- Prevented accidental clicks on destructive dialog actions such as `Do Not Load`, `Cancel`, and `No`.
+
+### Notes
+
+- This release focuses on reliable auto-launch behavior when Revit shows unsigned add-in security dialogs during startup.
+
+## [0.0.2] - 2026-04-10
+
+### Fixed
+
+- Fixed pytest plugin auto-loading via the `pytest11` entry point.
+- Fixed the `pytest_unconfigure` hook signature in `revitdevtool_pytest.plugin` so Pluggy accepts the plugin during pytest startup.
+- Restored the expected standalone package behavior so `RevitDevTool.PyTest` can be discovered and activated by a normal Python/pytest environment before connecting to Revit.
+
+### Changed
+
+- Aligned the published package metadata name with the recommended normalized package name `revitdevtool_pytest`.
+
+### Notes
+
+- This release is intended as a bugfix release for the `0.0.1` package.
+- No user-facing CLI options are changed in this release.
+- This name alignment is intended to remain compatible with existing PyPI installs because Python package indexes and installers normalize `.`, `-`, and `_` in distribution names.
+
+## [0.0.1] - 2026-04-09
+
+### Added
+
+- Initial standalone `pytest` plugin package for running Revit API tests through the RevitDevTool Named Pipe bridge.
+- Automatic discovery of running Revit instances through named pipes.
+- Optional Revit auto-launch flow via `--revit-launch` and `--revit-version`.
+- Remote test execution by intercepting `pytest_pyfunc_call` and forwarding serialized test code to Revit.
+- Support for explicit pipe targeting with `--revit-pipe`.
+- Per-test timeout and launch timeout configuration.
+- Revit startup dialog resolver integration.
+- Example test suite and VS Code integration guidance in the project documentation.
+
+### Notes
+
+- `0.0.1` introduced the core test bridge workflow, but the published package contains a plugin loading issue fixed in `0.0.2`.

revitdevtool_pytest-0.2.0/CLAUDE.md

@@ -0,0 +1 @@
+Refer to [AGENTS.md](./AGENTS.md) for project rules, conventions, and workflow.

revitdevtool_pytest-0.2.0/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: revitdevtool_pytest
+Version: 0.2.0
+Summary: pytest plugin for testing Revit API code via RevitDevTool Named Pipe bridge
+Project-URL: Homepage, https://github.com/trgiangv/RevitDevTool.PyTest
+Project-URL: Repository, https://github.com/trgiangv/RevitDevTool.PyTest
+Project-URL: Issues, https://github.com/trgiangv/RevitDevTool.PyTest/issues
+Author: Truong Giang Vu
+License-Expression: MIT
+License-File: LICENSE
+Keywords: bim,pytest,revit,revit-api,revitdevtool,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Requires-Dist: pytest>=9.0
+Requires-Dist: pywin32>=311
+Description-Content-Type: text/markdown
+
+# RevitDevTool.PyTest
+
+[![PyPI version](https://img.shields.io/pypi/v/RevitDevTool.PyTest)](https://pypi.org/project/RevitDevTool.PyTest/)
+[![Python](https://img.shields.io/pypi/pyversions/RevitDevTool.PyTest)](https://pypi.org/project/RevitDevTool.PyTest/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+pytest plugin for testing Revit API code via RevitDevTool Named Pipe bridge.
+Tests run inside a live Revit process — write standard pytest, execute remotely.
+
+## Installation
+
+```bash
+pip install revitdevtool_pytest
+```
+
+## Dependencies
+
+| Package | Version |
+|---|---|
+| Python | >= 3.10 |
+| pytest | >= 9.0 |
+| pywin32 | >= 311 |
+
+## Requirements
+
+- Windows (Named Pipes)
+- Revit with [RevitDevTool](https://github.com/trgiangv/RevitDevTool) add-in installed and loaded
+
+## Project Setup
+
+**Recommended:** scaffold your project with [uv](https://docs.astral.sh/uv/) or [pixi](https://pixi.sh/):
+
+```bash
+# uv
+uv init my-revit-tests
+cd my-revit-tests
+uv add revitdevtool_pytest
+
+# pixi (uses pyproject.toml as manifest)
+pixi init --format pyproject my-revit-tests
+cd my-revit-tests
+pixi add --pypi revitdevtool_pytest
+```
+
+## Configuration
+
+Add plugin settings to `[tool.pytest.ini_options]` in your `pyproject.toml`:
+
+```toml
+[tool.pytest.ini_options]
+revit_version = "2025"
+revit_launch = false
+revit_launch_timeout = "180"
+```
+
+| Option | Type | Default | Description |
+|---|---|---|---|
+| `revit_version` | string | — | Revit version year (e.g. `"2025"`). Required when `revit_launch = true`. |
+| `revit_launch` | bool | `false` | Force-launch a **new** Revit instance (skip reusing existing free instances). |
+| `revit_timeout` | string | `"60"` | Per-test execution timeout in seconds. |
+| `revit_launch_timeout` | string | `"120"` | Seconds to wait for Revit to start. |
+| `revit_pipe` | string | — | Explicit pipe name (bypasses auto-discovery). |
+
+CLI flags override INI settings:
+
+```bash
+pytest --revit-launch --revit-version=2025 -v
+```
+
+### Connection Behavior
+
+- **Default** (`revit_launch = false`): plugin auto-discovers a running Revit instance matching `revit_version` via Named Pipe scan. If none found, exits with error.
+- **Force launch** (`revit_launch = true`): always spawns a new Revit process, waits for its pipe to appear, then connects. Existing instances are ignored.
+
+### Print Output
+
+Captured `print()` output from tests running inside Revit is automatically shown in the terminal for passing tests (equivalent to `-rP`). No extra flags needed.
+
+## Usage
+
+### Fixtures
+
+Define fixtures in `conftest.py` that provide Revit API objects:
+
+```python
+import pytest
+
+@pytest.fixture(scope="session")
+def revit_uiapp():
+    return __revit__  # UIApplication injected by RevitDevTool
+
+@pytest.fixture(scope="session")
+def revit_app(revit_uiapp):
+    return revit_uiapp.Application
+
+@pytest.fixture(scope="session")
+def revit_doc(revit_uiapp):
+    return revit_uiapp.ActiveUIDocument.Document
+```
+
+### Writing Tests
+
+```python
+def test_active_view(revit_doc):
+    view = revit_doc.ActiveView
+    print(f"Active View: {view.Name}")
+    assert view.Name is not None
+
+def test_revit_version(revit_app):
+    assert "2025" in revit_app.VersionName
+```
+
+### PEP 723 Dependencies
+
+Declare test-suite dependencies in `conftest.py` using PEP 723 metadata. RevitDevTool auto-installs them before test execution:
+
+```python
+# /// script
+# dependencies = [
+#   "numpy>=2.0",
+#   "polars>=1.0",
+# ]
+# ///
+```
+
+### Running Tests
+
+```bash
+# With pyproject.toml configured:
+pytest
+
+# Override version for a single run:
+pytest --revit-version=2026 -v
+
+# Using uv or pixi:
+uv run pytest
+pixi run pytest
+```
+
+## How It Works
+
+1. pytest discovers and collects tests locally
+2. Plugin intercepts `pytest_runtestloop`, connects to Revit via Named Pipe
+3. Test nodeids are sent to Revit's `PytestRunner.py` (embedded in RevitDevTool)
+4. Tests execute inside Revit's Python.NET environment with full API access
+5. Results (pass/fail/skip, stdout, stderr, tracebacks) are returned via pipe
+6. Plugin maps results back to standard pytest reports
+
+## IDE Integration
+
+### VS Code / Cursor
+
+```json
+{
+    "python.testing.pytestEnabled": true,
+    "python.testing.pytestArgs": ["tests"]
+}
+```
+
+### PyCharm
+
+Enable pytest as the test runner. Plugin auto-detects IDE adapters and disables streaming to avoid duplicate results in the test tree.
+
+## License
+
+[MIT](LICENSE)

revitdevtool_pytest-0.2.0/README.md

@@ -0,0 +1,166 @@
+# RevitDevTool.PyTest
+
+[![PyPI version](https://img.shields.io/pypi/v/RevitDevTool.PyTest)](https://pypi.org/project/RevitDevTool.PyTest/)
+[![Python](https://img.shields.io/pypi/pyversions/RevitDevTool.PyTest)](https://pypi.org/project/RevitDevTool.PyTest/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+pytest plugin for testing Revit API code via RevitDevTool Named Pipe bridge.
+Tests run inside a live Revit process — write standard pytest, execute remotely.
+
+## Installation
+
+```bash
+pip install revitdevtool_pytest
+```
+
+## Dependencies
+
+| Package | Version |
+|---|---|
+| Python | >= 3.10 |
+| pytest | >= 9.0 |
+| pywin32 | >= 311 |
+
+## Requirements
+
+- Windows (Named Pipes)
+- Revit with [RevitDevTool](https://github.com/trgiangv/RevitDevTool) add-in installed and loaded
+
+## Project Setup
+
+**Recommended:** scaffold your project with [uv](https://docs.astral.sh/uv/) or [pixi](https://pixi.sh/):
+
+```bash
+# uv
+uv init my-revit-tests
+cd my-revit-tests
+uv add revitdevtool_pytest
+
+# pixi (uses pyproject.toml as manifest)
+pixi init --format pyproject my-revit-tests
+cd my-revit-tests
+pixi add --pypi revitdevtool_pytest
+```
+
+## Configuration
+
+Add plugin settings to `[tool.pytest.ini_options]` in your `pyproject.toml`:
+
+```toml
+[tool.pytest.ini_options]
+revit_version = "2025"
+revit_launch = false
+revit_launch_timeout = "180"
+```
+
+| Option | Type | Default | Description |
+|---|---|---|---|
+| `revit_version` | string | — | Revit version year (e.g. `"2025"`). Required when `revit_launch = true`. |
+| `revit_launch` | bool | `false` | Force-launch a **new** Revit instance (skip reusing existing free instances). |
+| `revit_timeout` | string | `"60"` | Per-test execution timeout in seconds. |
+| `revit_launch_timeout` | string | `"120"` | Seconds to wait for Revit to start. |
+| `revit_pipe` | string | — | Explicit pipe name (bypasses auto-discovery). |
+
+CLI flags override INI settings:
+
+```bash
+pytest --revit-launch --revit-version=2025 -v
+```
+
+### Connection Behavior
+
+- **Default** (`revit_launch = false`): plugin auto-discovers a running Revit instance matching `revit_version` via Named Pipe scan. If none found, exits with error.
+- **Force launch** (`revit_launch = true`): always spawns a new Revit process, waits for its pipe to appear, then connects. Existing instances are ignored.
+
+### Print Output
+
+Captured `print()` output from tests running inside Revit is automatically shown in the terminal for passing tests (equivalent to `-rP`). No extra flags needed.
+
+## Usage
+
+### Fixtures
+
+Define fixtures in `conftest.py` that provide Revit API objects:
+
+```python
+import pytest
+
+@pytest.fixture(scope="session")
+def revit_uiapp():
+    return __revit__  # UIApplication injected by RevitDevTool
+
+@pytest.fixture(scope="session")
+def revit_app(revit_uiapp):
+    return revit_uiapp.Application
+
+@pytest.fixture(scope="session")
+def revit_doc(revit_uiapp):
+    return revit_uiapp.ActiveUIDocument.Document
+```
+
+### Writing Tests
+
+```python
+def test_active_view(revit_doc):
+    view = revit_doc.ActiveView
+    print(f"Active View: {view.Name}")
+    assert view.Name is not None
+
+def test_revit_version(revit_app):
+    assert "2025" in revit_app.VersionName
+```
+
+### PEP 723 Dependencies
+
+Declare test-suite dependencies in `conftest.py` using PEP 723 metadata. RevitDevTool auto-installs them before test execution:
+
+```python
+# /// script
+# dependencies = [
+#   "numpy>=2.0",
+#   "polars>=1.0",
+# ]
+# ///
+```
+
+### Running Tests
+
+```bash
+# With pyproject.toml configured:
+pytest
+
+# Override version for a single run:
+pytest --revit-version=2026 -v
+
+# Using uv or pixi:
+uv run pytest
+pixi run pytest
+```
+
+## How It Works
+
+1. pytest discovers and collects tests locally
+2. Plugin intercepts `pytest_runtestloop`, connects to Revit via Named Pipe
+3. Test nodeids are sent to Revit's `PytestRunner.py` (embedded in RevitDevTool)
+4. Tests execute inside Revit's Python.NET environment with full API access
+5. Results (pass/fail/skip, stdout, stderr, tracebacks) are returned via pipe
+6. Plugin maps results back to standard pytest reports
+
+## IDE Integration
+
+### VS Code / Cursor
+
+```json
+{
+    "python.testing.pytestEnabled": true,
+    "python.testing.pytestArgs": ["tests"]
+}
+```
+
+### PyCharm
+
+Enable pytest as the test runner. Plugin auto-detects IDE adapters and disables streaming to avoid duplicate results in the test tree.
+
+## License
+
+[MIT](LICENSE)

{revitdevtool_pytest-0.0.3 → revitdevtool_pytest-0.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "revitdevtool_pytest"
-version = "0.0.3"
+version = "0.2.0"
 description = "pytest plugin for testing Revit API code via RevitDevTool Named Pipe bridge"
 readme = "README.md"
 license = "MIT"
@@ -36,3 +36,10 @@ Issues = "https://github.com/trgiangv/RevitDevTool.PyTest/issues"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/revitdevtool_pytest"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+revit_version = "2025"
+revit_timeout = "60"
+revit_launch = false
+revit_launch_timeout = "180"

{revitdevtool_pytest-0.0.3 → revitdevtool_pytest-0.2.0}/src/revitdevtool_pytest/__init__.py

@@ -1,3 +1,3 @@
 """RevitDevTool.PyTest: Run pytest tests inside a live Revit process via Named Pipe bridge."""
 
-__version__ = "0.0.1"
+__version__ = "0.2.0"