Skip to content

Tracking issue for MCP 861: Make the UI test suite more amenable to multiple editions #145364

@fmease

Description

@fmease

This is a tracking issue for MCP 861.

NOTE: The final syntax isn't fixed yet, we'll settle that in the impl'ing PR (e.g., [@]fmease has a strong preference for ..= over .., the latter is used in the MCP text).

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter or post in this Zulip topic.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

  • Implement the MCP
  • Adjust documentation

Unresolved questions

None so far.

Implementation history

Empty so far.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-compiletestArea: The compiletest test runnerB-MCP-approvedBlocker: Approved by an accepted MCP but not yet fully implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions