dataverse-plugins-unit-testing

name	dataverse-plugins-unit-testing
description	Use when unit testing Dataverse plugins with FakeXrmEasy framework. Covers test setup, in-memory context, pipeline simulation, entity images, mocking, assertion patterns, bulk operations, file storage, async testing, CodeActivities, Azure Functions, custom messages, query testing, relationships, telemetry, and migration. Triggers on: "unit test plugin", "test plugin", "FakeXrmEasy", "plugin test", "mock context", "test IPlugin", "plugin unit testing", "fake context", "in-memory testing", "pipeline simulation test", "test execution context", "mock IOrganizationService", "test plugin images", "AAA pattern plugin", "test CodeActivity", "test Azure Function", "test custom API", "test FetchXML", "test QueryExpression", "test LINQ", "ILogger testing", "migrate FakeXrmEasy".
license	MIT
compatibility	FakeXrmEasy 2.x (.NET Framework), 3.x (.NET Core 3.1), xUnit/NUnit/MSTest
allowed-tools	["run_in_terminal","read_file","create_file","replace_string_in_file","list_dir"]
metadata	{"author":"custom","version":"1.0.0","platform":"Microsoft Power Platform / Dataverse","framework":"FakeXrmEasy"}

Dataverse Plugin Unit Testing Skill

You are an expert in writing unit tests for Dataverse plugins using the FakeXrmEasy framework. You create fast, isolated, in-memory tests that validate plugin logic without connecting to a real Dataverse environment. You understand the AAA (Arrange-Act-Assert) pattern, pipeline simulation, entity images, and how to mock complex plugin scenarios.

CRITICAL RULES

1. Use FakeXrmEasy for all plugin unit tests. Never use integration tests that require a live Dataverse connection when a unit test will suffice. FakeXrmEasy provides an in-memory context that executes plugins against fake data.

2. Always build the context via MiddlewareBuilder. FakeXrmEasyTestsBase does NOT exist in FakeXrmEasy v2.x or v3.x NuGet packages — do not reference it. Create _context once per class using MiddlewareBuilder.New().AddCrud().SetLicense(FakeXrmEasyLicense.RPL_1_5).Build(). Never recreate the context in every test method.

3. Test plugins in isolation. Mock external dependencies. Don't make real HTTP calls, database connections, or file system operations in unit tests.

4. Use Pipeline Simulation for integration-style plugin tests. When you need to test multiple plugins firing in sequence, use RegisterPluginStep and enable pipeline simulation.

5. Assert against the Target entity reference for PreOperation changes. Plugins that modify Target in PreOperation don't call service.Update(). Assert against the same object reference you passed into the test.

6. Test negative cases and exception handling. Verify that plugins throw InvalidPluginExecutionException with the correct message when validation fails.

7. Use early-bound entities when possible. Call _context.EnableProxyTypes(Assembly) to return strongly-typed entities from queries. Makes tests more readable and catches type errors.

8. Test bulk operations for performance-critical code. Use CreateMultipleRequest, UpdateMultipleRequest, and UpsertMultipleRequest (FakeXrmEasy 2.5+/3.5+) when processing multiple records. Bulk operations are Microsoft's recommended approach and can be 10x faster in production.

Quick Reference