القائمة
Systematic activities that need to be performed after a release is done.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/microsoft/testfx --skill post-release-activitiesيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Grades a specified set of test methods individually and produces a concise table mapping each test (fully-qualified name) to a letter grade (A–F), a score band, pseudo-mutation resilience, a one-line note, and a concrete improvement for every grade below A — designed to be posted as a PR comment. Use when the caller wants per-test feedback on a curated list of methods (for example, the new or modified tests in a pull request), not a suite-wide audit. Polyglot: .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest/unittest), TS/JS (Jest/Vitest/Mocha/node:test), Java (JUnit/TestNG), Go, Ruby (RSpec/Minitest), Rust, Swift (XCTest/Swift Testing), Kotlin (JUnit/Kotest), PowerShell (Pester), C++ (GoogleTest/Catch2/doctest). Input is a list of test methods (or method bodies / file+line spans); output is a compact markdown table plus a short summary. DO NOT USE FOR: full suite audits (use test-quality-auditor agent or test-anti-patterns), writing new tests (use code-testing-generator agent or writing-mstest-tests), fixing
Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead).
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | post-release-activities |
| description | Systematic activities that need to be performed after a release is done. |
Use this skill when assigned an issue asking you to do the post-release activities. You will be given the branch name for the release. If that information is missing, ask for it and don't proceed with doing anything.
The branch name only contains the major and minor parts of the version, but not the patch part. To find the full version:
eng/Versions.props file in the given branch.VersionPrefix.Create a tag for the branch using the version you found in Step 1. The tag name should be v{version} (replace {version} with the version you found in Step 1). After creating the tag, push it to the remote repository.
release-notes.md and add the following content to it: See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#{version}) (replace {version} with the version you found in Step 1).gh release create v{version} --draft --title v{version} --notes-file release-notes.md.gh api --method POST -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/microsoft/testfx/releases/generate-notes -f 'tag_name=v{version}' (replace {version} with the version you found in Step 1).docs/Changelog.md and Microsoft.Testing.Platform changes go to docs/Changelog-Platform.md.main branch, not the release branch.Open a PR to the release branch to update the patch version in eng/Versions.props file. The new patch version should be one more than the patch version you found in Step 1.
Note that in this step, both TestingPlatformVersionPrefix and VersionPrefix must be updated.
Open a PR to the main branch to update the minor version in eng/Versions.props file. The new minor version should be one more than the minor version you found in Step 1, and the patch version should be reset to 0.
Note that in this step, both TestingPlatformVersionPrefix and VersionPrefix must be updated.
Open a PR to the main branch to update the product versions of public samples to latest. Public samples are present in samples/public directory.
eng/mark-shipped.ps1 (requires PowerShell 7.0).src/Analyzers/MSTest.Analyzers/AnalyzerReleases.Unshipped.md (except the first two lines that start with ;) to src/Analyzers/MSTest.Analyzers/AnalyzerReleases.Shipped.md.Create a PR to main with these changes.