tester.testing-patterns

Testing instructions for DataFactory.MCP.Tests, the project’s .NET test suite, using xUnit, a framework for automated tests.

In plain words
What is it for?
Use it to run all tests, select a test, collect coverage, or write unit and parameterized tests for DataFactory.MCP.
Why use it?
It keeps tests in the expected location and provides consistent commands and naming patterns for checking code behavior.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/microsoft/datafactory.mcp/tester.testing-patterns
Any agent
npx skills add microsoft/DataFactory.MCP --skill tester.testing-patterns
Clone the repo
git clone --depth 1 https://github.com/microsoft/DataFactory.MCP

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 598 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00598
Opus 5 $0.00015 $0.00299
Sonnet 5 $0.00006 $0.00120
Haiku 4.5 $0.00003 $0.00060

Measured 2d ago against content hash 9d7364143ec2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tester.testing-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/tester.testing-patterns/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing in DataFactory.MCP

Test Stack

  • Framework: xUnit ([Fact], [Theory], [InlineData])
  • Runner: xunit.runner.visualstudio
  • Skippable: Xunit.SkippableFact ([SkippableFact], Skip.If(...))
  • Coverage: coverlet
  • Target: net10.0

Test Location

All tests live in DataFactory.MCP.Tests/.

Commands

Task Command
Run all dotnet test
Verbose dotnet test -v normal
Filter dotnet test --filter "FullyQualifiedName~TestName"
Coverage dotnet test --collect:"XPlat Code Coverage"

Naming Convention

MethodName_Scenario_ExpectedResult

Examples:

  • Authenticate_WithValidCredentials_ReturnsToken
  • ListGateways_WhenNotAuthenticated_ThrowsException
  • CreateConnection_WithInvalidType_ReturnsError

Test Patterns

Unit Test (Arrange-Act-Assert)

public class MyServiceTests
{
    [Fact]
    public void MethodName_Scenario_ExpectedResult()
    {
        // Arrange
        var service = new MyService();

        // Act
        var result = service.DoSomething();

        // Assert
        Assert.NotNull(result);
        Assert.Equal("expected", result.Value);
    }
}

Parameterized Tests

[Theory]
[InlineData("input1", "expected1")]
[InlineData("input2", "expected2")]
public void MethodName_WithVariousInputs_ReturnsExpected(string input, string expected)
{
    var result = MyService.Process(input);
    Assert.Equal(expected, result);
}

Skippable Tests (for environment-dependent tests)

[SkippableFact]
public void IntegrationTest_RequiresAuth()
{
    Skip.If(string.IsNullOrEmpty(Environment.GetEnvironmentVariable("AZURE_CLIENT_ID")),
        "Requires Azure credentials");
    // test body
}

What to Test

  • Tools: Parameter validation, response formatting, error handling
  • Services: API call construction, response parsing, error translation
  • Models: Serialization/deserialization roundtrips
  • Edge cases: Null inputs, empty collections, unauthenticated state, API errors

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 100 lines · 31 tokens per session scan A 9d7364143ec2

Subscribe to this mod's changes

tester.testing-patterns is a skill published in the GitHub repository microsoft/DataFactory.MCP (42 stars, last pushed 20d ago), licensed MIT. It adds 31 tokens to every session and 598 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens