cashtab does not use the bip39 dependency as all the logic needed is available in ecash-lib

however you do need to include the english wordlist somewhere here to lose the dep; not necessarily related to this diff but opportunity to lose a critical external dep

not sure what we gain by testing this; of course we expect the app to never have an invalid mnemonic

would make more sense to test this kind of behavior on import, e.g. we correctly throw or show correct validation error if user attempts to import an invalid mnemonic

it's usually a bad sign if arbitrary timeouts are in like this, especially one for 60s. If this is failing without the timeout there could be some other issue, but more likely the expectation should simply be cleaned up somehow.

cypress has async expectors (I think this is one).

It's possible there is some need for longer timeouts for CI processing, but this should be handled at he CI config level, not hard coded timeouts on individual checks

again here, not sure testing isValidMnemonic at this stage is useful or relevant to app performance. We shouldn't really be using isValidMnemonic in the test file at all.

A test that would make sense would be

• user enters a 12 word phrase that is not a valid mnemonic
• user sees validation error and import button is disabled (or user attempts to import and sees expected modal, whatever the expected behavior is)
• user corrects mnemonic and imports successfully

current use of this function is not adding value to the test