Constrain Test column width in grade-tests PR comment

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3

[Amaury Levé (Evangelink)]

Fixes the horizontal-scroll problem in the test-quality grade PR comment that the bot posts when a PR touches tests.

Before

The bot rendered a markdown pipe-table where the Test column put the fully-qualified test name (Namespace.ClassName.MethodName) inside backticks. GitHub renders backtick spans as non-wrapping <code>, so long MSTest names overflowed the PR-comment width and forced a horizontal scroll bar.

After

• Switch the table from a markdown pipe-table to a raw HTML <table> with a <colgroup> that caps each column to a fixed percentage of the comment width (6% / 50% / 7% / 9% / 28%). GitHub's HTML sanitizer honors the width attribute on <table>, <col>, <th>, and <td>, so the columns stay within the PR-comment width.
• Drop the namespace prefix from the displayed name (show ClassName.MethodName, never Namespace.ClassName.MethodName). Disambiguation moves to Notes if two graded methods would otherwise collide.
• Use raw <code>…</code> HTML tags instead of backtick spans so nested <wbr> actually takes effect (backtick code spans render content literally in GFM, so a <wbr> inside backticks would display as the literal text <wbr>).
• Inject invisible <wbr> soft-wrap hints after each _ in long PascalCase MSTest names so the constrained 50%-wide cell can actually wrap on long names like TestNodeResultsState_GetSingleActiveOrSummaryTask_WhenEmpty_ReturnsNull. <wbr> does not change what copy-paste yields.
• Promote the (new) / (modified) marker out of the Test cell into its own narrow first column so it no longer competes for the cell width.

Files changed

• .github/workflows/shared/grade-tests-shared.md — Step 4 ("Post the comment")

The two consumer workflows (grade-tests-on-pr.agent.md and grade-tests.agent.md) pull this body at runtime via {{#runtime-import …}}, so the .lock.yml files do not change.

Validation

• gh aw compile grade-tests-on-pr.agent grade-tests.agent --strict → 0 errors, 0 warnings.

[Copilot]

Pull request overview

Updates the shared grade-tests workflow guidance so the bot’s PR comment renders without horizontal scrolling when test names are long, by switching from a Markdown pipe-table to a constrained-width HTML table and by adding soft-wrap hints within <code>.

Changes:

• Replaces the Markdown pipe-table example with an HTML <table> using a fixed-width <colgroup> layout.
• Updates the table rules to require HTML <table> output and to display shortened test names (dropping namespaces) with <wbr> wrap hints.

Show a summary per file

File	Description
.github/workflows/shared/grade-tests-shared.md	Changes the “Post the comment” guidance to use a fixed-width HTML table and wrap-friendly <code> content to prevent horizontal scrolling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 3