The BB_RPC_URL_HTTP_ethereum GitHub variable still pointed to an
internal sldev.cz backend. Removed ethereum from CI env blocks and
EVM_COINS filter until a public endpoint is configured.
Remaining CI-tested chains: avalanche, bsc, arbitrum, base, optimism, polygon.
The Go test framework runs ALL coins listed in tests.json with
'connectivity' enabled, falling back to default config URLs when
env vars are absent. This exposed internal infrastructure (127.0.0.1
defaults and sldev.cz URLs) in CI logs.
Now both connectivity-tests and integration-tests always apply an
EVM-only coin filter (avalanche|bsc|arbitrum|base|ethereum|optimism|polygon)
unless a manual workflow_dispatch provides a custom coin_filter.
UTXO chains remain fully testable on the dev server.
UTXO chains (bitcoin, bcash, dogecoin, litecoin, zcash) use internal
backends unreachable from GitHub-hosted runners. Removed them from
the CI env blocks so connectivity and integration tests only run
against publicly reachable EVM endpoints (quicknode).
UTXO chains are still fully tested on the dev server where internal
backends are accessible.
- Add workflow_dispatch trigger with inputs: coin_filter, run_unit_tests,
run_connectivity_tests, run_integration_tests
- coin_filter accepts regex (e.g. 'bitcoin', 'ethereum', 'bitcoin|ethereum|bsc')
- Integration tests (rpc + sync) are manual-only (default off) since they
are heavy and require live backends
- Connectivity tests run automatically on push/PR, or manually with filter
- Unit tests can be skipped in manual runs to speed up targeted testing
Replace bash/curl connectivity tests with the Go-based connectivity
test suite from the integration test framework. The CI now uses
'make test-connectivity' which runs TestIntegration/.*/connectivity
via go test, matching the same pattern as unit and integration tests.
Backend URLs are read from GitHub Actions variables (BB_RPC_URL_HTTP_*,
BB_RPC_URL_WS_*) and forwarded into Docker by the Makefile's BB_RPC_ENV.
