Enforce signalize testing patterns with count assertions and cleanup helpers.
npx skills add https://github.com/spearwolf/signalize --skill signalize-testing
Please help me install this Agent Skill. Skill: signalize-testing Source: https://github.com/spearwolf/signalize/tree/main/skills/signalize-testing Command: npx skills add https://github.com/spearwolf/signalize --skill signalize-testing
Testing signalize code helps ensure there are no leaked signals, effects, or links, and that tests don't interfere with each other.
Apply these testing patterns to validate cleanup, isolation, and correct lifecycle behavior of signalize components in your codebase.
High-intent search queries and answers about installing and using this skill.
Testing signalize code requires applying cleanup patterns using destroySignal and SignalGroup to ensure resources are released after tests. Count-based assertions like getSignalsCount and getEffectsCount verify that no signals or effects have leaked across your test suite.
Isolating signalize test state requires using beforeEach and afterEach test setup practices to maintain isolation and detect leaks early. These test helpers ensure deterministic results by preventing tests from interfering with each other.
You can assert counts for signals, effects, and links by using getSignalsCount, getEffectsCount, and getLinksCount assertions. These count-based assertions verify a clean state and ensure reliable lifecycle behavior across your signalize test suite.
Verifying the lifecycle and behavior of effects and batches ensures deterministic test results in signalize. Applying targeted testing patterns validates that effects execute correctly and resources are properly cleaned up.
Using SignalGroup instead of destroySignal depends on your test cleanup patterns for managing multiple resources. SignalGroup aggregates signals for batch cleanup, while destroySignal targets individual signal resources to prevent leaks.
kapilvirenahujaGenerate baseline-tests.yaml from blast-radius.yaml for uncovered code coverage gaps.
slantviewDiagnose production incidents and deployment failures through log analysis and container debugging.
Svenja-devEnforce strict test-driven development by blocking code generation until tests exist.
timequityAudit test suites to replace mock-focused assertions with real-behavior checks.
