Skip to content

test(notifications): end-to-end recap orchestration test (build → format → both channels) #2252

Description

@JSONbored

Integration-style unit test that exercises runMaintainerRecap end to end with stubbed data sources and a fetch stub: builds a RecapReport, formats it, and fans out to both the Discord and Slack deliverers, asserting redaction holds across the whole pipeline and that a single-channel outage doesn't abort the other. Pure test bounty — lands after the builder/formatter/delivery bounties, no product code beyond test wiring.

Deliverables

  • test/unit/maintainer-recap.test.ts driving runMaintainerRecap with injected aggregators + a fetch stub
  • Assert: both channels called when both webhooks set; Discord failure still lets Slack deliver (and vice versa); a report seeded with a reward/path term is redacted in BOTH channel payloads
  • Cover the flag-OFF short-circuit branch so coverage stays 97% branch-counted

References

  • src/services/notify-discord.ts:75
  • src/services/notify-discord.ts:117
  • src/signals/redaction.ts:48

Part of #1963.


size: XS · held for later release (gittensor:bug once activated)

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.gittensor:priorityMaintainer-selected Gittensor priority — scores a 1.5x multiplier.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions