meridian-test-writer

Generate xUnit tests by applying a scenario-first approach that exercises real production-style code paths across provider ingestion, pipeline/storage, and execution seams using named market simulations. It enforces Meridian-specific quality guardrails like async correctness and observable assertions.

Writing FluentAssertions tests for F# interop components is best handled by generating scenario-first xUnit tests that apply Pattern I multi-layer market simulations. The generated tests follow strict isolation and naming conventions to ensure consistent observable assertions.

To stop async void issues and enforce cancellation timeouts in xUnit tests, generate them using built-in quality guardrails that mandate async correctness, proper await using disposal, and strict isolation. This prevents common test anti-patterns automatically.

Yes, you can use scenario-first testing for WPF UI services and endpoint integrations. The test generator applies market-event simulations across these specific component seams while enforcing proper file cleanup practices and observable assertions.

Generating tests this way aligns directly with Lens 4 Test Code Quality checklist requirements. The structured outputs satisfy the code review criteria by enforcing naming conventions, cancellation timeouts, isolation, and proper async disposal automatically.

Limitations include strict dependencies on following Meridian test quality rules, requiring proper await using disposal and no shared mutable state. Tests must adhere to these architectural constraints to successfully execute the bundled Pattern I multi-layer scenario simulations.