ghubstan 39cda43208 Add LongRunningTradesTest ... This new api testcase can run long series' of regtest trades by looping over modified TakeBuyBTCOfferTest and TakeSellBTCOfferTest cases. The purpose is to help reproduce problems and isolate bugs Bisq's core and api layers. LongRunningTradesTest is not enabled by default; it will not run in a default test environment (such a Travis CI). Enviornment variable LONG_RUNNING_TRADES_TEST_ENABLED must exist for the test to run. The env variable can be set in a bash shell before running the test case in a shell (using a gradle command), or the environment variable can be set in an Intellij test launcher's Evironment variables field. The modifed (short running) TakeBuyBTCOfferTest and TakeSellBTCOfferTest cases run as before. Changes include: - Add static boolean isLongRunningTest to AbstractOfferTest. - Add looping control Supplier maxTradeStateAndPhaseChecks to AbstractTradeTest. It uses the isLongRunningTest flag in the superclass to help define the wait times for trade state/phase changes during short and long running tests. - Made AbstractTradeTest assert(true, trade.isDepositPublished) conditional upon isLongRunningTest value. Long running trade test asserts have to be looser due to increasing latency of wallet, offer and trade operations in the server as the trade counts increase. - Overload ApiTestCase#startSupportingApps with additional flag: startSupportingAppsInDebugMode. Default is false. This makes starting background apps in debug mode a bit more convenient and self explanatory.		2021-03-19 21:21:02 +01:00
..
docs	Make codacy happy (I hope)	2021-03-18 14:49:57 -03:00
scripts	Fix getunusedbsqaddress test	2021-02-27 22:58:22 -03:00
src	Add LongRunningTradesTest	2021-03-19 21:21:02 +01:00
dao-setup.gradle	Delete commented statement	2020-07-13 19:48:59 -03:00