e2e tests for feature 'validate rpc' PR#99 #100
Merged
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
ghost
assigned 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Relates to #76
Added tests:
Custom Rpc
✓ switches to settings screen through menu 'Network -> Custom RPC' (139ms)
✓ error message if new Rpc url is invalid (999ms)
✓ error message if new Rpc url has no HTTP/HTTPS prefix (2383ms)
✓ error message if Rpc doesn't exist (2472ms)
✓ user can add valid custom rpc (13421ms)
✓ new added Rpc displayed in network dropdown menu (417ms)
✓ click button 'Delete' opens screen 'Delete Custom RPC' (1392ms)
✓ click button 'No' opens screen 'Settings' (392ms)
✓ user able to delete custom rpc (623ms)
✓ deleted custom rpc isn't displayed in 'Settings' screen (157ms)
✓ deleted custom rpc isn't displayed in network dropdown menu (3802ms)