test(nip66): add integration tests for RelayMonitorWorker - #733
Conversation
Add @nip-66 Cucumber scenarios that exercise the monitor worker against real Redis and the integration relay, covering snapshot storage, disabled mode, target fallback, and invalid target skipping.
🦋 Changeset detectedLatest commit: d72782c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
coverage: 70.601% (+0.4%) from 70.218% — nip66-integration-tests into main |
There was a problem hiding this comment.
Pull request overview
This PR adds Cucumber-based integration coverage for the NIP-66 RelayMonitorWorker, validating that probe runs persist the latest snapshot into Redis and that target selection behaves correctly (explicit targets, info.relay_url fallback, and invalid target skipping).
Changes:
- Added
@nip-66Cucumber feature scenarios asserting snapshot persistence/status and target resolution behavior. - Added step definitions that run
RelayMonitorWorkeragainst the integration relay and poll Redis for the latest snapshot. - Added a changeset describing the new integration test coverage.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| test/integration/features/nip-66/nip-66.feature.ts | Adds step definitions that start RelayMonitorWorker, configure settings, and assert Redis snapshot contents. |
| test/integration/features/nip-66/nip-66.feature | Adds NIP-66 feature scenarios for enabled/disabled behavior, fallback targeting, and invalid target skipping. |
| .changeset/nip66-relay-monitor-integration-tests.md | Declares a patch changeset documenting the added integration tests. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| const createMonitorProcess = (): NodeJS.Process => new EventEmitter() as NodeJS.Process | ||
|
|
Description
This PR:
Related Issue
#724 (merged)
Motivation and Context
How Has This Been Tested?
pnpm run docker:test:integration -- --tags @nip-66Screenshots (if appropriate):
Types of changes
Checklist: