288498ccdc
Why this change is needed: The test file was using a custom TestResults class for tracking test execution and results, which is not standard practice for pytest-based test suites. This makes the tests harder to integrate with CI/CD pipelines and reduces compatibility with pytest plugins and tooling. How it solves it: - Removed custom TestResults class and manual result tracking - Added @pytest.mark.asyncio decorator to all async test functions - Converted all results.add() calls to standard pytest assert statements - Added pytest fixture (setup_shared_data) for common test setup - Removed custom main() runner (pytest handles test discovery/execution) - Kept all test logic, assertions, and debugging print statements intact Impact: - All 11 test functions maintain identical behavior and coverage - Tests now follow pytest conventions and integrate with pytest ecosystem - Test output is cleaner and more informative with pytest's reporting - Easier to run selective tests using pytest's filtering options Testing: Verified by running: uv run pytest tests/test_workspace_isolation.py -v Result: All 11 tests passed in 2.41s |
||
|---|---|---|
| .. | ||
| test_aquery_data_endpoint.py | ||
| test_curl_aquery_data.sh | ||
| test_graph_storage.py | ||
| test_lightrag_ollama_chat.py | ||
| test_postgres_retry_integration.py | ||
| test_workspace_isolation.py | ||
| test_write_json_optimization.py | ||