Skip to content

Add nigiri setup and e2e tests to CI pipeline#1

Open
qustavo wants to merge 2 commits into
mainfrom
add-e2e-tests-to-pipeline
Open

Add nigiri setup and e2e tests to CI pipeline#1
qustavo wants to merge 2 commits into
mainfrom
add-e2e-tests-to-pipeline

Conversation

@qustavo

@qustavo qustavo commented Mar 24, 2026

Copy link
Copy Markdown
Owner

Install nigiri, start the network, and run e2e tests in CI.

@qustavo qustavo force-pushed the add-e2e-tests-to-pipeline branch 5 times, most recently from a855c76 to 670b28c Compare March 24, 2026 21:06
Add comprehensive end-to-end testing:
- E2E test covering full L402 payment flow
- Test verifies proxy strips Authorization headers before upstream
- Tests use real LND backend via nigiri
- CLN tests skipped pending nigiri REST API fix

Improve nigiri network setup script:
- Add CI environment detection for --ci flag
- Wait for chopsticks (faucet) service readiness
- Wait for LND credentials to be written to volumes
- Generate and save CLN rune for test access

Set up GitHub Actions CI/CD:
- Create separate e2e.yml workflow for integration tests
- Install nigiri and start test network in CI
- Add tmate for interactive debugging on failures
- Keep main go.yml pipeline fast (unit tests + linting only)

This allows fast feedback on unit tests while running slower
e2e tests in parallel.

Signed-off-by: Gustavo Chain <me@qustavo.cc>
@qustavo qustavo force-pushed the add-e2e-tests-to-pipeline branch from 670b28c to 8fcbbb6 Compare March 24, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant