-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
test(suite-native): Import an already imported XPUB #12518
Conversation
@@ -23,6 +23,19 @@ class AccountImportActions { | |||
await scrollUntilVisible(by.text(accountName)); | |||
} | |||
|
|||
async importSameAccount({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this method is unnecessary, pls use importAccount
for this test's purposes.
}) { | ||
await this.selectCoin({ networkSymbol }); | ||
await this.submitXpub({ xpub, isValid: true }); | ||
await detoxExpect(element(by.text('Coin already synced'))).toBeVisible(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While onging expects are fine inside a page action method (eg if you want to assert/wait for something during the test), this is the final assert of the test which should always
be in the IT
part of the test, not iside the logic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we have this scenarion already covered in suite-native/app/e2e/tests/invalidAccountsImport.test.ts
@Nodonisko you are right, i have not noticed it. |
Automatized tests of sanity test Import an already imported XPUB
https://www.notion.so/satoshilabs/Import-an-already-imported-XPUB-c15497dd8e3340618c17029745f11aab?pvs=4