Standardised test reporting

Open
#486 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ci-cd, testing-qa

Research direction

Start by locating how the conformance tests currently produce and expose their results, then review the needs of JUnit-compatible reporting and GitHub pull request tools. Done means an option produces a standard test report that other testing tools can consume and summarize on a GitHub PR.

Written by the indexing model from the issue text.

Description

enhancement

It would be great to output a report in some kind of standardised test reporting format like junit

Describe the solution you'd like
An option to output a test report that is compatible with other standard testing tools. For example to be able to take the results and put a summary on a github PR.

Dominant language
TypeScript
Stars
127
Forks
101
Avg merge
6d 1h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/conformance

All issues in modelcontextprotocol/conformance

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.