General

# General

* Always write tests for new code
* Prefer integration tests over unit tests
* Keep documentation in sync with code
* Use TUnit for tests
* Write readable and maintainable code

## Testing

This project uses **TUnit** as the test framework and **AwesomeAssertions** for assertions.

**IMPORTANT**: AwesomeAssertions is a fork of FluentAssertions. Except for the using statement, the API is **identical** to FluentAssertions.

```csharp
// Use AwesomeAssertions (FluentAssertions API)
result.Should().Be(expected);
collection.Should().HaveCount(5);
act.Should().Throw<InvalidOperationException>();
```

See `tests/Ratatoskr.Tests/AGENTS.md` for detailed testing instructions.

## Running all tests
`dotnet run --project tests/Ratatoskr.Tests/Ratatoskr.Tests.csproj`

## Running filtered tests
`dotnet run --project tests/Ratatoskr.Tests/Ratatoskr.Tests.csproj -- --treenode-filter "/<Assembly>/<Namespace>/<Class name>/<Test name>"` (without the angled brackets)

Example: `dotnet run --project tests/Ratatoskr.Tests/Ratatoskr.Tests.csproj -- --treenode-filter "/*/*/OutboxTests/*"`

### Filter Operators

TUnit supports several operators for building complex filters:

* Wildcard matching: Use `*` for pattern matching (e.g., `LoginTests*` matches `LoginTests`, `LoginTestsSuite`, etc.)
* Equality: Use `=` for exact match (e.g., `[Category=Unit]`)
* Negation: Use `!=` for excluding values (e.g., `[Category!=Performance]`)
* AND operator: Use `&` to combine conditions (e.g., `[Category=Unit]&[Priority=High]`)
* OR operator: Use `|` to match either condition within a single path segment - requires parentheses (e.g., `/*/*/(Class1)|(Class2)/*`)