CtrlK
BlogDocsLog inGet started
Tessl Logo

golikovichev/phoenix2pytest

Turn labeled LLM failure traces from an Arize Phoenix project into runnable pytest regression tests using the phoenix2pytest pipeline. Use when the user has an LLM application emitting OpenInference spans to Phoenix and wants a regression suite from real production failures, when extracting test cases from observed LLM bugs (hallucination, format break, off-topic drift, stale data, wrong reasoning, refusal bug), when bridging Phoenix-labeled traces into pytest-based suites for CI, when the user mentions Arize Phoenix MCP, OpenInference instrumentation, LLM observability, Gemini test synthesis, Vertex AI agent evaluation, or wants to react to LLM failures rather than predict them upfront.

88

1.63x
Quality

94%

Does it follow best practices?

Impact

98%

1.63x

Average score across 2 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

SECURITY.md

Security Policy

Supported Versions

phoenix2pytest is in early development (0.x). Security fixes ship on the latest main branch only.

VersionSupported
Latest mainyes
Older 0.x tagsno

Reporting a Vulnerability

Please report security issues privately through GitHub Private vulnerability reporting on this repository.

If GitHub reporting is not available to you, email the maintainer at golikovichev@gmail.com with the subject [security] phoenix2pytest.

What to expect after a report:

  • Acknowledgement within 7 days.
  • A fix or mitigation plan within 30 days for confirmed issues.
  • Credit in the release notes once the fix ships, unless you prefer to remain anonymous.

Please do not file public issues for suspected vulnerabilities.

CHANGELOG.md

CONTRIBUTING.md

README.md

REFERENCE.md

SECURITY.md

SKILL.md

tessl.json

tile.json