• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cameri / nostream / 41229750741
78%

Build:
DEFAULT BRANCH: main
Ran 31 Oct 2026 06:33PM UTC
Jobs 2
Files 319
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

31 Oct 2026 06:30PM UTC coverage: 77.211% (+0.5%) from 76.759%
41229750741

push

github

web-flow
test(payments): add unit tests for the zebedee, opennode, nodeless and lnurl processors (#917)



## Description
Adds unit specs for the four payment processors that had none, next to
the existing lnbits and nwc ones (`test/unit/payments-processors/`). No
production code changes.

For each processor:
- `createInvoice`: the request sent to the provider (url, body, amount
unit, callback url / metadata, ttl) and the mapping of the response to
an `Invoice`; msats are converted to whole sats where the provider takes
sats; provider outages and responses without data are not swallowed.
- `getInvoice`: the request, every provider status mapped to
`InvoiceStatus` (a status the provider adds later is never read as
paid), confirmation dates, and error propagation.
- processor specifics: OpenNode's `lightning_invoice` / `lightning`
fallback and `amount` / `price` fallback; Nodeless's 15 minute fallback
expiry; LNURL's generated invoice id and verify-url polling.

## Related Issue
Closes #903

## Motivation and Context
These are the money-moving code paths for four providers. A misread
status or a wrong amount unit is a funds bug, and nothing covered them.

## How Has This Been Tested?
- The new specs pass (58 tests). Reverting a status mapping in
`transform.ts` or changing OpenNode's ttl makes the matching spec fail.
- `pnpm lint`, `pnpm check:deps`, `pnpm run build:check`, `pnpm run
test:unit`.

## Screenshots (if appropriate):

## Types of changes
- [x] Non-functional change (docs, style, minor refactor)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)

## Checklist:
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [x] I have added tests to ... (continued)

4341 of 6162 branches covered (70.45%)

Branch coverage included in aggregate %.

9496 of 11759 relevant lines covered (80.76%)

778.32 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Integration - 41229750741.1 31 Oct 2026 06:33PM UTC 319
33.47
GitHub Action Run
2 Unit - 41229750741.2 31 Oct 2026 06:35PM UTC 319
74.58
GitHub Action Run
Source Files on build 41229750741
  • Tree
  • List 319
  • Changed 5
  • Source Changed 0
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #41229750741
  • b1efa6e4 on github
  • Prev Build on main (#41228990797)
  • Next Build on main (#41231981006)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc