btcpayserver/BTCPayServer.Tests
2019-01-15 22:12:29 +09:00
..
Lnd Remove Lightning Specific logic from BTCPay, and use BTCPayServer.Lightning packages instead 2018-08-30 12:24:00 +09:00
Logging Make ChargeListener use only one websocket connection per url 2018-02-26 13:29:23 +09:00
Mocks Refactor the RateProvider 2018-05-03 03:32:42 +09:00
Properties Adopt dotnet core editorconfig, big reformating 2017-10-27 17:53:04 +09:00
BTCPayServer.Tests.csproj Add tooling which pull transifex translation automatically, add SlovenĨina. (Close #386) 2018-11-14 16:48:25 +09:00
BTCPayServerTester.cs Added new disable-registration command line option. 2019-01-06 16:43:55 +01:00
ChangellyTests.cs fix issue with changelly rates and cover with UTs (#368) 2018-10-28 23:07:36 +09:00
ChargeTester.cs Remove Lightning Specific logic from BTCPay, and use BTCPayServer.Lightning packages instead 2018-08-30 12:24:00 +09:00
CoinSwitchTests.cs initial coinswitch work 2018-12-11 12:47:38 +01:00
CrowdfundTests.cs bug fixes and optimizations 2019-01-05 19:47:39 +01:00
CustomerHttpServer.cs Improve IPN tests 2019-01-06 15:04:30 +09:00
docker-bitcoin-cli.ps1 Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-bitcoin-cli.sh Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-compose.yml switc back to regtest 2019-01-05 10:18:01 +01:00
docker-customer-lightning-cli.ps1 Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-customer-lightning-cli.sh Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-entrypoint.sh Show test logs in CircleCI 2018-12-20 18:35:32 +09:00
docker-litecoin-cli.ps1 Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-litecoin-cli.sh Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-merchant-lightning-cli.ps1 Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
docker-merchant-lightning-cli.sh Fix all script because of docker-compose team screwing up (https://github.com/docker/compose/issues/6316) 2018-11-22 16:16:10 +09:00
Dockerfile Run tests inside container 2018-12-18 22:35:58 +09:00
LightningDTester.cs Remove Lightning Specific logic from BTCPay, and use BTCPayServer.Lightning packages instead 2018-08-30 12:24:00 +09:00
ProcessLauncher.cs Adopt dotnet core editorconfig, big reformating 2017-10-27 17:53:04 +09:00
RateRulesTest.cs Change test trait name 2018-10-28 22:51:02 +09:00
README.md Properly configure the logger to log what happen in ConfigureServices, add https profile adapted for debugging ledger wallet. 2018-11-01 12:52:32 +09:00
ServerTester.cs Add support for removing network fee on first payment 2019-01-05 17:45:49 +09:00
TestAccount.cs Remove uneeded database call during derivation scheme registration 2019-01-06 17:58:11 +09:00
UnitTest1.cs Round up invoice price 2019-01-15 22:12:29 +09:00
UtilitiesTests.cs check for disable flag 2018-12-11 22:18:17 -07:00
Utils.cs Adopt dotnet core editorconfig, big reformating 2017-10-27 17:53:04 +09:00
xunit.runner.json Add xunit diagnostic message 2018-12-20 21:00:06 +09:00

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

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?

  1. Run docker-compose down --v (this will reset your test environment)
  2. Run docker-compose pull (this will ensure you have the lastest images)
  3. Run again with docker-compose up dev

If you still have issues, try to restart docker.