Validate duraflows workflows with Vitest tests using in-memory doubles and fixed clocks.
npx skills add https://github.com/camcima/duraflows --skill duraflows-tester
Please help me install this Agent Skill. Skill: duraflows-tester Source: https://github.com/camcima/duraflows/tree/main/skills/duraflows-tester Command: npx skills add https://github.com/camcima/duraflows --skill duraflows-tester
This guide provides structured testing patterns for validating duraflows workflows using Vitest, enabling deterministic, self-contained tests that do not require real databases or external services.
Write Vitest tests that create an in-memory runtime, inject a fixed clock, mock commands, and assert the correct state transitions and history.
High-intent search queries and answers about installing and using this skill.
You can test duraflows workflows deterministically by using Vitest with in-memory test doubles for instances and history, eliminating the need for real databases or external services. This approach ensures reproducible state transitions and test outcomes.
Validating state transitions and timeouts in Vitest involves injecting a fixed clock to control time-based moves and using mock commands to assert correct history. This pattern verifies guard decisions and timeout processing across multiple scenarios reproducibly.
Yes, Vitest mocking can simulate command success, failure, and best-effort outcomes for workflow tests. Mock commands replace real dependencies, allowing you to verify observer correlation and onEnter chains in a controlled environment.
The best way to test workflow guards and ref-name validation is by setting up an in-memory runtime with Vitest. This self-contained environment allows you to exercise guard decisions and verify ref-name validation logic without external service dependencies.
No, duraflows testing with Vitest does not require external dependencies or running services. Tests are fully self-contained, relying on in-memory test doubles, fixed clocks, and mock commands to verify state transitions and observers deterministically.
Workflow timeout tests become flaky with real time because actual execution delays cause non-deterministic behavior. Injecting a fixed clock in Vitest allows you to control timeout processing and verify time-driven state transitions reproducibly.
eykdParse GWT specifications and generate executable tests for Vitest.
UvRoxxRun and debug Midnight contract tests using Vitest simulators.
vecearAutomate MSW-based API and service mocks with fixtures and test overrides.
haxlysImplement Jest, Vitest, and Testing Library test suites for JavaScript/TypeScript projects.
