5b3b96b372
* GreenField: Payment Requests CRUD * fixes * fix swagger * fix swag * rebase fixes * Add new permissions for payment requests * Adapt PR to archive * fix tst * add to contains policxy * make decimals returned as string due to avoid shitty language parsing issues * do not register decimal json converter as global * fix cultureinfo for json covnerter * pr changes * add json convertet test * fix json test * fix rebase |
||
---|---|---|
.. | ||
Lnd | ||
Logging | ||
Mocks | ||
Properties | ||
TestData | ||
ApiKeysTests.cs | ||
BTCPayServer.Tests.csproj | ||
BTCPayServerTester.cs | ||
ChangellyTests.cs | ||
ChargeTester.cs | ||
CheckoutUITests.cs | ||
CoinSwitchTests.cs | ||
CrowdfundTests.cs | ||
CustomerHttpServer.cs | ||
docker-bitcoin-cli.ps1 | ||
docker-bitcoin-cli.sh | ||
docker-bitcoin-generate.ps1 | ||
docker-bitcoin-generate.sh | ||
docker-compose.monero.yml | ||
docker-compose.yml | ||
docker-customer-lightning-cli.ps1 | ||
docker-customer-lightning-cli.sh | ||
docker-elements.ps1 | ||
docker-entrypoint.sh | ||
docker-litecoin-cli.ps1 | ||
docker-litecoin-cli.sh | ||
docker-merchant-lightning-cli.ps1 | ||
docker-merchant-lightning-cli.sh | ||
Dockerfile | ||
ElementsTests.cs | ||
Extensions.cs | ||
FakeServer.cs | ||
GreenfieldAPITests.cs | ||
LightningDTester.cs | ||
MockDelay.cs | ||
PayJoinTests.cs | ||
PaymentHandlerTest.cs | ||
PaymentRequestTests.cs | ||
ProcessLauncher.cs | ||
PSBTTests.cs | ||
RateRulesTest.cs | ||
README.md | ||
SeleniumTester.cs | ||
SeleniumTests.cs | ||
ServerTester.cs | ||
sshd.Dockerfile | ||
StorageTests.cs | ||
TestAccount.cs | ||
TestUtils.cs | ||
U2FTests.cs | ||
UnitTest1.cs | ||
UtilitiesTests.cs | ||
Utils.cs | ||
xunit.runner.json |
How to be started for development
BTCPay Server tests depend on having a proper environment running with Postgres, Bitcoind, NBxplorer configured.
You can however use the docker-compose.yml
of this folder to get it running.
In addition, when you run a debug session of BTCPay (Hitting F5 on Visual Studio Code or Visual Studio 2017), it will run the launch profile called Docker-Regtest
. This launch profile depends on this docker-compose
running.
This is running a bitcoind instance on regtest, a private bitcoin blockchain for testing on which you can generate blocks yourself.
docker-compose up dev
You can run the tests while it is running through your favorite IDE, or with
dotnet test
Once you want to stop
docker-compose down
If you want to stop, and remove all existing data
docker-compose down --v
You can run tests on MySql
database instead of Postgres
by setting environnement variable TESTS_DB
equals to MySql
.
How to manually test payments
Using the test bitcoin-cli
You can call bitcoin-cli inside the container with docker exec
, for example, if you want to send 0.23111090
to mohu16LH66ptoWGEL1GtP6KHTBJYXMWhEf
:
./docker-bitcoin-cli.sh sendtoaddress "mohu16LH66ptoWGEL1GtP6KHTBJYXMWhEf" 0.23111090
If you are using Powershell:
.\docker-bitcoin-cli.ps1 sendtoaddress "mohu16LH66ptoWGEL1GtP6KHTBJYXMWhEf" 0.23111090
You can also generate blocks:
.\docker-bitcoin-generate.ps1 3
Using the test litecoin-cli
Same as bitcoin-cli, but with .\docker-litecoin-cli.ps1
and .\docker-litecoin-cli.sh
instead.
Using the test lightning-cli
If you are using Linux:
./docker-customer-lightning-cli.sh pay lnbcrt100u1pd2e6uspp5ajnadvhazjrz55twd5k6yeg9u87wpw0q2fdr7g960yl5asv5fmnqdq9d3hkccqpxmedyrk0ehw5ueqx5e0r4qrrv74cewddfcvsxaawqz7634cmjj39sqwy5tvhz0hasktkk6t9pqfdh3edmf3z09zst5y7khv3rvxh8ctqqw6mwhh
If you are using Powershell:
.\docker-customer-lightning-cli.ps1 pay lnbcrt100u1pd2e6uspp5ajnadvhazjrz55twd5k6yeg9u87wpw0q2fdr7g960yl5asv5fmnqdq9d3hkccqpxmedyrk0ehw5ueqx5e0r4qrrv74cewddfcvsxaawqz7634cmjj39sqwy5tvhz0hasktkk6t9pqfdh3edmf3z09zst5y7khv3rvxh8ctqqw6mwhh
If you get this message:
{ "code" : 205, "message" : "Could not find a route", "data" : { "getroute_tries" : 1, "sendpay_tries" : 0 } }
Please, run the test CanSetLightningServer
, this will establish a channel between the customer and the merchant, then, retry.
FAQ
docker-compose up dev
failed or tests are not passing, what should I do?
- Run
docker-compose down --v
(this will reset your test environment) - Run
docker-compose pull
(this will ensure you have the lastest images) - Run again with
docker-compose up dev
If you still have issues, try to restart docker.