Siemens.AspNet.CodeRules.MSTest 7.7.4

Siemens.AspNet.CodeRules.MSTest

One setup class. Every code rule becomes its own MSTest test. No test classes to write.

Runs code rules as MSTest tests. You register your rules in one ICodeRuleSetup; a source generator (shipped inside this package) reads the registrations at build time and writes one test per rule, grouped into one test class per group. Test Explorer, dotnet test, filters by category and CI test results work as for any other test.

public sealed class CodeRuleSetup : ICodeRuleSetup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddCodeRuleEngine("My.slnx", o => o.AddRulePack<NamingRulePack>());
    }
}

That is the whole test project.

Quick start

1. Create a normal MSTest project (Microsoft.NET.Test.Sdk, MSTest.TestAdapter, MSTest.TestFramework).

2. Add the adapter and your rule packs:

   dotnet add package Siemens.AspNet.CodeRules.MSTest
   dotnet add package My.Team.CodeRules          # a rule pack, or write rules directly in this project
   

3. Add exactly one class that implements ICodeRuleSetup (see above) and register the rules with AddRule<TRule>(), Add<TRule>(), AddRulePack<TPack>() or AddRulesFrom(typeof(X).Assembly).

4. Build and run dotnet test.

The package brings the engine, the contracts and the source generator. One PackageReference, nothing else to wire up.

Optional: <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles> writes the generated tests to obj/.../generated/CodeRules.MsTest.g.cs so you can read them without the IDE.

What you get

• One test per rule, one test class per group: CodeRules.Generated.Code, CodeRules.Generated.Solution, CodeRules.Generated.Controllers, ...
• Test name <ID>_<ClassName> when the rule ID is a constant string, otherwise the class name.
• Categories CodeRules, CodeRules <Group> and CodeRules <Tag>: dotnet test --filter "TestCategory=CodeRules Naming"
• Rules from packs and local rules of the test project; a rule the setup does not register gets no test.
• Compiled packs get the same tests as rules in source: ID, title and tags come from the pack's [assembly: CodeRuleDescriptor] (written by the generator in Siemens.AspNet.CodeRules.Contracts).
• Skipped rules (IRule.SkipReason, SkipRule<TRule>(reason)) show up as [Ignore]d tests with the reason.
• A guard test fails when a registered rule has no generated test, so no rule is silently lost.
• Parallel by design: the engine creates every context once and thread safe; the solution is parsed once per test run. Add [assembly: Parallelize(Scope = ExecutionScope.MethodLevel)] to run the rule tests in parallel.

A failing rule

The environment variable wins over the setup. Order, .runsettings example: Output mode.

Build warnings

Also runs in the CLI

Referencing this package makes the project a code rule project: build/Siemens.AspNet.CodeRules.MSTest.props sets <IsCodeRuleProject>true</IsCodeRuleProject> (only as a default, set it to false to opt out). The coderules CLI (Siemens.AspNet.CodeRules.Cli) finds such projects and runs the same ICodeRuleSetup natively, without a test host:

dotnet tool install -g Siemens.AspNet.CodeRules.Cli
coderules run                 # same rules, same result as dotnet test
coderules run --format ai     # one JSON document for AI agents and scripts

Related packages

License

Copyright (c) Siemens AG. See LICENSE.md in the package.