nano_test_network => nano_dev_network, new nano_test_network #2877
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
August 6, 2020 20:27
development tests to run on nano_dev_network
…-node tests easier without conflicting with the live network
# Conflicts: # nano/core_test/block_store.cpp # nano/core_test/ledger.cpp nano::test_* in core_test renamed nano::dev_*
argakiig
added
enhancement
universe
argakiig
changed the title
guilhermelawless
approved these changes
Aug 11, 2020
SergiySW
approved these changes
Aug 12, 2020
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR would migrate the existing nano_test_network to the nano_dev_network as tests are typically only run for development purposes and free up the nano_test_network to allow for a test network to be created that would have the same network values as the main network but allow for integration testing and other service testing without having to use the live network.
Currently the new nano_test_network has not been deployed, but the intent behind putting this in now as opposed to later would eliminate further rebasing or merging as other tests come into the develop branch with the existing nano_test_network and nano::test_*