Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom bisq.properties to API test harness #5718

Merged
merged 1 commit into from
Sep 23, 2021

Conversation

ghubstan
Copy link
Contributor

This change adds a bisq.properties file to apitest/src/main/resources, and makes sure it is copied to regtest/dev bisq instances' app data dirs before they are started. By default it is empty, but can be used to override default BisqApp options during ad-hoc testing.

The change was necessary because the core's bisq.properties resource is not copied to test harness bisq instance's regtest data dirs during a normal build.

This PR's branch is based off master, is not part of any series of PRs requiring reviewing and merging in chronological order.

This change adds a bisq.properties file to apitest/src/main/resources,
and makes sure it is copied to regtest/dev bisq instances' app data dirs
before they are started.  By default it is empty, but can be used to
override default BisqApp options during ad-hoc testing.

The change was necessary because the core's bisq.properties resource is
not copied to test harness bisq instance's regtest data dirs during a normal
build.
Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@ripcurlx ripcurlx added this to the v1.7.5 milestone Sep 23, 2021
@ripcurlx ripcurlx merged commit 4849988 into bisq-network:master Sep 23, 2021
@ghubstan ghubstan deleted the pickup-core-bisq-properties branch November 10, 2021 13:09
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.

2 participants