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

GetStartedPages: automated tests #2659

Merged
merged 47 commits into from
Jan 28, 2021
Merged

GetStartedPages: automated tests #2659

merged 47 commits into from
Jan 28, 2021

Conversation

bgptr
Copy link
Collaborator

@bgptr bgptr commented Sep 7, 2020

This is the continuation of #2606. I focus this time to GetStartedPage components:

  • AdvancedStartup
  • CreateWalletPage
  • CreateWalletPage/ConfirmSeed
  • CreateWalletPage/CopySeed
  • CreateWalletPage/ExistingSeed
  • LanguageSelectPage
  • Logs
  • OpenWallet
  • PreCreateWallet
  • PrivacyPage
  • ReleaseNotes
  • RescanWallet (implemented in [Rescan] functional Rescan & RescanProgress components #2710)
  • SetMixedAcctPage
  • Settings
  • SpvChoicePage
  • TrezorConfig
  • TutorialPage
  • WalletSelection

@bgptr bgptr force-pushed the test-getstarted branch 3 times, most recently from 5cd17cd to e5c65ad Compare September 17, 2020 20:15
@bgptr bgptr changed the title [wip] GetStartedPages: automated tests GetStartedPages: automated tests Oct 12, 2020
@amass01
Copy link
Member

amass01 commented Oct 13, 2020

Please add closes #2660 to the description.

@bgptr bgptr force-pushed the test-getstarted branch 4 times, most recently from 72bebcd to 772dacc Compare October 20, 2020 14:53
Copy link
Member

@vctt94 vctt94 left a comment

Choose a reason for hiding this comment

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

Very good job on this PR!

Having tests will make life much easier for next release, thanks for pushing that forward.

I left some small comments, but I think if you could also add some docs on how to properly make tests that would be great!

Right now I am only running yarn test, is that enough?

@bgptr
Copy link
Collaborator Author

bgptr commented Oct 21, 2020

Thank you for your review.

Running yarn test is absolutely fine. Optionally you can create coverage reports by running yarn test --coverage and run yarn test-watch during development to rerun only the related tests of changed files. I've added a README.md file to the test folder with this info.

Copy link
Member

@vctt94 vctt94 left a comment

Choose a reason for hiding this comment

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

Thanks! LGTM!

@bgptr bgptr force-pushed the test-getstarted branch 2 times, most recently from 26fd508 to d7632a8 Compare November 11, 2020 19:11
bgptr added 26 commits January 28, 2021 18:06
- AdvancedStartupHeader never used
- isRemoteValid function call is unnecessary in onSubmitRemoteForm. The submit button is disabled until the form is not valid.
- isAppDataValid function call is unnecessary in onSubmitAppDataForm. The submit button is disabled until the form is not valid.
update AnimatedLinearProgressFull test,  PrivacyPage test, update walletSelection (ask for passphrase if account discovery is needed) and createWallet test
add daemon warning test
- privacy option has removed
- add piui checkbox support
- specify more Wallet Name label
dx
@alexlyp alexlyp merged commit 6e03baf into decred:master Jan 28, 2021
@bgptr bgptr deleted the test-getstarted branch February 9, 2021 18:24
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.

4 participants