[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADEEYRP0W2F2KHV887XTZN":3,"skill-same:01M6ADEEYRP0W2F2KHV887XTZN":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6ADEEYRP0W2F2KHV887XTZN","csharp-tunit",null,"Get best practices for TUnit unit testing, including data-driven tests","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcsharp-tunit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"csharp","csharp tunit","tunit","testing","best practices","data","unit testing","get","tests","driven","unit","for","data-driven","2026-11-10 10:12:30",false,"---\nname: csharp-tunit\ndescription: 'Get best practices for TUnit unit testing, including data-driven tests'\n---\n\n# TUnit Best Practices\n\nYour goal is to help me write effective unit tests with TUnit, covering both standard and data-driven testing approaches.\n\n## Project Setup\n\n- Use a separate test project with naming convention `[ProjectName].Tests`\n- Reference TUnit package and TUnit.Assertions for fluent assertions\n- Create test classes that match the classes being tested (e.g., `CalculatorTests` for `Calculator`)\n- Use .NET SDK test commands: `dotnet test` for running tests\n- TUnit requires .NET 8.0 or higher\n\n## Test Structure\n\n- No test class attributes required (like xUnit\u002FNUnit)\n- Use `[Test]` attribute for test methods (not `[Fact]` like xUnit)\n- Follow the Arrange-Act-Assert (AAA) pattern\n- Name tests using the pattern `MethodName_Scenario_ExpectedBehavior`\n- Use lifecycle hooks: `[Before(Test)]` for setup and `[After(Test)]` for teardown\n- Use `[Before(Class)]` and `[After(Class)]` for shared context between tests in a class\n- Use `[Before(Assembly)]` and `[After(Assembly)]` for shared context across test classes\n- TUnit supports advanced lifecycle hooks like `[Before(TestSession)]` and `[After(TestSession)]`\n\n## Standard Tests\n\n- Keep tests focused on a single behavior\n- Avoid testing multiple behaviors in one test method\n- Use TUnit's fluent assertion syntax with `await Assert.That()`\n- Include only the assertions needed to verify the test case\n- Make tests independent and idempotent (can run in any order)\n- Avoid test interdependencies (use `[DependsOn]` attribute if needed)\n\n## Data-Driven Tests\n\n- Use `[Arguments]` attribute for inline test data (equivalent to xUnit's `[InlineData]`)\n- Use `[MethodData]` for method-based test data (equivalent to xUnit's `[MemberData]`)\n- Use `[ClassData]` for class-based test data\n- Create custom data sources by implementing `ITestDataSource`\n- Use meaningful parameter names in data-driven tests\n- Multiple `[Arguments]` attributes can be applied to the same test method\n\n## Assertions\n\n- Use `await Assert.That(value).IsEqualTo(expected)` for value equality\n- Use `await Assert.That(value).IsSameReferenceAs(expected)` for reference equality\n- Use `await Assert.That(value).IsTrue()` or `await Assert.That(value).IsFalse()` for boolean conditions\n- Use `await Assert.That(collection).Contains(item)` or `await Assert.That(collection).DoesNotContain(item)` for collections\n- Use `await Assert.That(value).Matches(pattern)` for regex pattern matching\n- Use `await Assert.That(action).Throws\u003CTException>()` or `await Assert.That(asyncAction).ThrowsAsync\u003CTException>()` to test exceptions\n- Chain assertions with `.And` operator: `await Assert.That(value).IsNotNull().And.IsEqualTo(expected)`\n- Use `.Or` operator for alternative conditions: `await Assert.That(value).IsEqualTo(1).Or.IsEqualTo(2)`\n- Use `.Within(tolerance)` for DateTime and numeric comparisons with tolerance\n- All assertions are asynchronous and must be awaited\n\n## Advanced Features\n\n- Use `[Repeat(n)]` to repeat tests multiple times\n- Use `[Retry(n)]` for automatic retry on failure\n- Use `[ParallelLimit\u003CT>]` to control parallel execution limits\n- Use `[Skip(\"reason\")]` to skip tests conditionally\n- Use `[DependsOn(nameof(OtherTest))]` to create test dependencies\n- Use `[Timeout(milliseconds)]` to set test timeouts\n- Create custom attributes by extending TUnit's base attributes\n\n## Test Organization\n\n- Group tests by feature or component\n- Use `[Category(\"CategoryName\")]` for test categorization\n- Use `[DisplayName(\"Custom Test Name\")]` for custom test names\n- Consider using `TestContext` for test diagnostics and information\n- Use conditional attributes like custom `[WindowsOnly]` for platform-specific tests\n\n## Performance and Parallel Execution\n\n- TUnit runs tests in parallel by default (unlike xUnit which requires explicit configuration)\n- Use `[NotInParallel]` to disable parallel execution for specific tests\n- Use `[ParallelLimit\u003CT>]` with custom limit classes to control concurrency\n- Tests within the same class run sequentially by default\n- Use `[Repeat(n)]` with `[ParallelLimit\u003CT>]` for load testing scenarios\n\n## Migration from xUnit\n\n- Replace `[Fact]` with `[Test]`\n- Replace `[Theory]` with `[Test]` and use `[Arguments]` for data\n- Replace `[InlineData]` with `[Arguments]`\n- Replace `[MemberData]` with `[MethodData]`\n- Replace `Assert.Equal` with `await Assert.That(actual).IsEqualTo(expected)`\n- Replace `Assert.True` with `await Assert.That(condition).IsTrue()`\n- Replace `Assert.Throws\u003CT>` with `await Assert.That(action).Throws\u003CT>()`\n- Replace constructor\u002FIDisposable with `[Before(Test)]`\u002F`[After(Test)]`\n- Replace `IClassFixture\u003CT>` with `[Before(Class)]`\u002F`[After(Class)]`\n\n**Why TUnit over xUnit?**\n\nTUnit offers a modern, fast, and flexible testing experience with advanced features not present in xUnit, such as asynchronous assertions, more refined lifecycle hooks, and improved data-driven testing capabilities. TUnit's fluent assertions provide clearer and more expressive test validation, making it especially suitable for complex .NET projects.\n","# TUnit Best Practices\n\nYour goal is to help me write effective unit tests with TUnit, covering both standard and data-driven testing approaches.\n\n## Project Setup\n\n- Use a separate test project with naming convention `[ProjectName].Tests`\n- Reference TUnit package and TUnit.Assertions for fluent assertions\n- Create test classes that match the classes being tested (e.g., `CalculatorTests` for `Calculator`)\n- Use .NET SDK test commands: `dotnet test` for running tests\n- TUnit requires .NET 8.0 or higher\n\n## Test Structure\n\n- No test class attributes required (like xUnit\u002FNUnit)\n- Use `[Test]` attribute for test methods (not `[Fact]` like xUnit)\n- Follow the Arrange-Act-Assert (AAA) pattern\n- Name tests using the pattern `MethodName_Scenario_ExpectedBehavior`\n- Use lifecycle hooks: `[Before(Test)]` for setup and `[After(Test)]` for teardown\n- Use `[Before(Class)]` and `[After(Class)]` for shared context between tests in a class\n- Use `[Before(Assembly)]` and `[After(Assembly)]` for shared context across test classes\n- TUnit supports advanced lifecycle hooks like `[Before(TestSession)]` and `[After(TestSession)]`\n\n## Standard Tests\n\n- Keep tests focused on a single behavior\n- Avoid testing multiple behaviors in one test method\n- Use TUnit's fluent assertion syntax with `await Assert.That()`\n- Include only the assertions needed to verify the test case\n- Make tests independent and idempotent (can run in any order)\n- Avoid test interdependencies (use `[DependsOn]` attribute if needed)\n\n## Data-Driven Tests\n\n- Use `[Arguments]` attribute for inline test data (equivalent to xUnit's `[InlineData]`)\n- Use `[MethodData]` for method-based test data (equivalent to xUnit's `[MemberData]`)\n- Use `[ClassData]` for class-based test data\n- Create custom data sources by implementing `ITestDataSource`\n- Use meaningful parameter names in data-driven tests\n- Multiple `[Arguments]` attributes can be applied to the same test method\n\n## Assertions\n\n- Use `await Assert.That(value).IsEqualTo(expected)` for value equality\n- Use `await Assert.That(value).IsSameReferenceAs(expected)` for reference equality\n- Use `await Assert.That(value).IsTrue()` or `await Assert.That(value).IsFalse()` for boolean conditions\n- Use `await Assert.That(collection).Contains(item)` or `await Assert.That(collection).DoesNotContain(item)` for collections\n- Use `await Assert.That(value).Matches(pattern)` for regex pattern matching\n- Use `await Assert.That(action).Throws\u003CTException>()` or `await Assert.That(asyncAction).ThrowsAsync\u003CTException>()` to test exceptions\n- Chain assertions with `.And` operator: `await Assert.That(value).IsNotNull().And.IsEqualTo(expected)`\n- Use `.Or` operator for alternative conditions: `await Assert.That(value).IsEqualTo(1).Or.IsEqualTo(2)`\n- Use `.Within(tolerance)` for DateTime and numeric comparisons with tolerance\n- All assertions are asynchronous and must be awaited\n\n## Advanced Features\n\n- Use `[Repeat(n)]` to repeat tests multiple times\n- Use `[Retry(n)]` for automatic retry on failure\n- Use `[ParallelLimit\u003CT>]` to control parallel execution limits\n- Use `[Skip(\"reason\")]` to skip tests conditionally\n- Use `[DependsOn(nameof(OtherTest))]` to create test dependencies\n- Use `[Timeout(milliseconds)]` to set test timeouts\n- Create custom attributes by extending TUnit's base attributes\n\n## Test Organization\n\n- Group tests by feature or component\n- Use `[Category(\"CategoryName\")]` for test categorization\n- Use `[DisplayName(\"Custom Test Name\")]` for custom test names\n- Consider using `TestContext` for test diagnostics and information\n- Use conditional attributes like custom `[WindowsOnly]` for platform-specific tests\n\n## Performance and Parallel Execution\n\n- TUnit runs tests in parallel by default (unlike xUnit which requires explicit configuration)\n- Use `[NotInParallel]` to disable parallel execution for specific tests\n- Use `[ParallelLimit\u003CT>]` with custom limit classes to control concurrency\n- Tests within the same class run sequentially by default\n- Use `[Repeat(n)]` with `[ParallelLimit\u003CT>]` for load testing scenarios\n\n## Migration from xUnit\n\n- Replace `[Fact]` with `[Test]`\n- Replace `[Theory]` with `[Test]` and use `[Arguments]` for data\n- Replace `[InlineData]` with `[Arguments]`\n- Replace `[MemberData]` with `[MethodData]`\n- Replace `Assert.Equal` with `await Assert.That(actual).IsEqualTo(expected)`\n- Replace `Assert.True` with `await Assert.That(condition).IsTrue()`\n- Replace `Assert.Throws\u003CT>` with `await Assert.That(action).Throws\u003CT>()`\n- Replace constructor\u002FIDisposable with `[Before(Test)]`\u002F`[After(Test)]`\n- Replace `IClassFixture\u003CT>` with `[Before(Class)]`\u002F`[After(Class)]`\n\n**Why TUnit over xUnit?**\n\nTUnit offers a modern, fast, and flexible testing experience with advanced features not present in xUnit, such as asynchronous assertions, more refined lifecycle hooks, and improved data-driven testing capabilities. TUnit's fluent assertions provide clearer and more expressive test validation, making it especially suitable for complex .NET projects.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcsharp-tunit",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add github\u002Fawesome-copilot --skill csharp-tunit",{"tool":58,"command":59},"bunx","bunx skills add github\u002Fawesome-copilot --skill csharp-tunit",{"tool":61,"command":62},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill csharp-tunit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcsharp-tunit\u002FSKILL.md",true,[],[67,97,124,154,188,205],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":77,"publishedAt":37},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[73,74],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[78,79,80,81,82,83,84,85,86,87,88,89,90,91,32,92,93,94,95,96],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","prove","use","users","functions","with",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":37},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[103],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,108,109,110,35,111,112,113,114,115,116,117,118,119,120,121,122,123],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":37},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[137,138,139,140,141,142,35,82,143,144,145,146,147,148,149,93,150,151,152,153],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":37},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,83,181,182,183,184,185,35,186,187],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":192,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":201,"publishedAt":37},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[196,197,200],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":198,"categoryName":199,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},[202,108,175,203,204],"resemble detect","https","identity",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":192,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":37},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},[217,218,219,220,138,84,9,107,221,222,203,223,224,225,226,227,228,229,230,231,232,233,32,234,235,236,237],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]