-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
108 additions
and
4 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
Feature: State Sync Namespace | ||
|
||
Scenario: Full Node Starts Block By Block Sync From Genesis In A Network At Height 4 | ||
# Given there are 4 staked validators | ||
When the developer runs the command "TriggerView" | ||
Then wait for the network to reach height "4" | ||
# And a full node joins the network | ||
# Then querying the height of the full node should return 0 | ||
# And querying the height of the full node should return 4 | ||
|
||
# Trigger a view | ||
# send a debug command -> debug helper | ||
# Wait for all the validators in the network to go to the next height | ||
# Continuously query their height -> use QUery Height | ||
# How do I guarantee I'm reaching everyone -> PeerStore | ||
# Add a full node to the network | ||
# Update the local config | ||
# Start a full node | ||
# Connect to the network | ||
# Query the height of the full node | ||
# Wait for the full node to sync | ||
# Continuously query the height of the full node | ||
# How do I know when it's done syncing -> Query the height of the network | ||
|
||
|
||
# Future Scenarios | ||
# Scenario: Full Node Starts Block By Block Sync From Height 2 In A Network At Height 4 | ||
# Scenario: Full Node Starts Sync From Snapshot At Height 2 In A Network At Height 4 | ||
# ??? |
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
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