[weekly-issue-activity] Weekly Summary - 2026-06-22

[Evangelink]

📊 Weekly Overview

During the week of June 15–22, 2026, 16 new issues were opened in microsoft/testfx, more than doubling the 7 issues opened the prior week (June 8–15). The repository currently has 89 open issues in total. The surge is largely driven by automated tooling — the majority of this week's new issues are bot-generated duplicate-code detection reports, monthly performance tracking items, and test-gap activity tracking. One notable organic contribution includes a user-reported bug in TestExecutionManager and a community discussion about dotnet test filtering ergonomics.

⚠️ Data note: Closed issues data was unavailable this cycle due to an API timeout during collection. Metrics for closed counts and resolution times are estimated or omitted where indicated.

---

📈 Issue Activity Trends

Weekly Activity Patterns

Issue-opening activity has been accelerating through June, with the week of June 15 seeing the highest single-week count (13–16 opened depending on day-of-week cutoff). The running total of open issues has grown steadily from ~58 a month ago to 89 today, suggesting that issues are accumulating faster than they are being closed. The partial current week (Jun 22 only) shows 3 new issues already opened, consistent with the accelerating pace.

Resolution Time Analysis

The 7-day moving average of daily issue-opening rate has climbed sharply in the last two weeks, peaking around June 19–21. This spike coincides with a batch of automated duplicate-code and performance-tracking issues being filed. The baseline rate (excluding automation spikes) appears to be 1–2 issues/day organically.

i️ Exact resolution time (avg/median days to close) is unavailable this cycle. This chart shows the daily opening rate as a proxy for activity intensity.

---

🔑 Key Trends

• Automation-driven issue volume: A large fraction of this week's new issues are bot-generated (type/automation), including [duplicate-code], [perf-improver], [test-improver], and [efficiency-improver] monthly tracking issues. These inflate the opened count significantly.
• MTP dominates the backlog: area/mtp labels account for 40 of 89 open issues (~45%), making Microsoft.Testing.Platform the highest-priority area by volume.
• Growing needs/triage queue: 9 open issues are still awaiting triage, and 9 require design discussion (needs/design), suggesting a bottleneck in issue classification and decision-making.
• Breaking changes in flight: 10 open issues are tagged type/breaking-change, indicating active API-breaking work that may need careful release planning.
• Organic user issues remain low: Only 1–2 genuinely user-filed bug reports this week (TestExecutionManager Task.WhenAll loses its source tasks to GC #9183, Microsoft Testing Platform: dotnet test filtering ergonomics and discoverability differ from VSTest #9273), which is a healthy signal — the repo is stable from an end-user perspective.

---

📋 Summary Statistics

Metric	This Week (Jun 15–22)	Last Week (Jun 8–15)	Trend
Issues Opened	16	7	↑ +129%
Issues Closed	N/A	N/A	—
Currently Open	89	~73 (est.)	↑
Avg Close Time	N/A	N/A	—

Full Issue List — This Week (Jun 15–22, 16 issues opened)

1. [duplicate-code] Duplicate Code: TestResultCapture.TryCapture body duplicated across HtmlReport, JUnitReport, and CtrfReport extensions #9319 — [duplicate-code] Duplicate Code: TestResultCapture.TryCapture body duplicated across HtmlReport, JUnitReport, and CtrfReport extensions — @Evangelink — type/tech-debt, type/automation
2. [duplicate-code] Duplicate Code: StackTraceHelper regex initialization block duplicated across Platform and MSBuild projects with diverged patter [Content truncated due to length] #9317 — [duplicate-code] Duplicate Code: StackTraceHelper regex initialization duplicated — @Evangelink — type/tech-debt, type/automation
3. [duplicate-code] Duplicate Code: ApplicationStateGuard utility class copied across 4 projects with behavioral divergence #9316 — [duplicate-code] Duplicate Code: ApplicationStateGuard utility class copied across projects — @Evangelink — type/tech-debt, type/automation
4. [perf-improver] Track performance regressions in CI: integrate MSTest.Performance.Runner timing output #9312 — [perf-improver] Track performance regressions in CI: integrate MSTest performance tracking — @Evangelink — area/performance, type/automation
5. [duplicate-code] Duplicate Code: Cooperative-Cancellation Timeout Block in FixtureMethodRunner and TestMethodInfo #9306 — [duplicate-code] Duplicate Code: Cooperative-Cancellation Timeout Block duplicated — @Evangelink — type/tech-debt, type/automation
6. [duplicate-code] Duplicate Code: CtrfReportEngine Reimplements Shared File-Naming Utilities #9304 — [duplicate-code] Duplicate Code: CtrfReportEngine reimplements shared logic — @Evangelink — type/tech-debt, type/automation
7. [duplicate-code] Duplicate Code: STA Thread Dispatch Pattern in MSTest Adapter #9303 — [duplicate-code] Duplicate Code: STA Thread Dispatch Pattern in MSTest duplicated — @Evangelink — type/tech-debt, type/automation
8. Temporarily disabled LocalizationTests/LocalizationFailingTests until OneLocBuild ships proper TerminalResources translations #9295 — Temporarily disabled LocalizationTests/LocalizationFailingTests — @Evangelink — (no labels)
9. [duplicate-code] Duplicate Code Detector - Issue Group #9280 — [duplicate-code] Duplicate Code Detector - Issue Group — @Evangelink — type/tech-debt, type/automation
10. Microsoft Testing Platform: dotnet test filtering ergonomics and discoverability differ from VSTest #9273 — Microsoft Testing Platform: dotnet test filtering ergonomics and discoverability — @Evangelink — external/xunit
11. [perf-improver] Monthly Activity 2026-06 #9258 — [perf-improver] Monthly Activity 2026-06 — @Evangelink — area/performance, type/automation
12. [test-improver] Monthly Activity 2026-06 #9224 — [test-improver] Monthly Activity 2026-06 — @Evangelink — type/test-gap, type/automation
13. [efficiency-improver] Monthly Activity 2026-06 #9197 — [efficiency-improver] Monthly Activity 2026-06 — @Evangelink — area/performance, type/automation
14. TestExecutionManager Task.WhenAll loses its source tasks to GC #9183 — TestExecutionManager Task.WhenAll loses its source tasks to GC — (external contributor) — needs/triage, external/other
15. New extension: Microsoft.Testing.Extensions.GitHubActionsReport (groups, annotations, step summary) #9142 — New extension: Microsoft.Testing.Extensions.GitHubActionsReport (grouped annotations) — @Evangelink — (no labels)
16. Extend AzureDevOpsReport extension: log groups, failure annotations, raw-log progress mirror #9141 — Extend AzureDevOpsReport extension: log groups, failure annotations, rich summary — @Evangelink — (no labels)

---

💡 Recommendations for Upcoming Week

1. Triage the 9 needs/triage issues — The triage queue has grown; clearing it keeps the backlog healthy and ensures user-reported bugs get routed correctly.
2. Review the 10 type/breaking-change issues — With 10 active breaking-change items open, the team should assess whether any are blocking a release window or need to be deferred.
3. Evaluate automation noise vs. signal — Many new issues are bot-generated. Consider whether [duplicate-code] and [perf-improver] auto-issues need to be batched or throttled to avoid inflating triage workload.
4. Prioritize TestExecutionManager Task.WhenAll loses its source tasks to GC #9183 (TestExecutionManager GC bug) — This is a user-filed potential correctness bug with no assignee; it warrants prompt triage and reproduction.
5. Re-enable LocalizationTests (Temporarily disabled LocalizationTests/LocalizationFailingTests until OneLocBuild ships proper TerminalResources translations #9295) — The temporarily disabled localization tests represent a known gap; tracking its resolution prevents it from being forgotten.

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Weekly Issue Summary workflow. · 554.7 AIC · ⌖ 13.1 AIC · ⊞ 37.9K · [◷]( · ◷)

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/weekly-issue-activity.md@main

• expires on Jun 29, 2026, 6:43 AM UTC

[Evangelink]

This discussion has been marked as outdated by Weekly Issue Summary.

A newer discussion is available at Discussion #9494.