aboutsummaryrefslogtreecommitdiffstats
path: root/test/integration/lib/first-time.js
Commit message (Collapse)AuthorAgeFilesLines
* Fix vault encrypting & unlocking bugDan Finlay2016-12-011-0/+2
| | | | | | | | This is only a bug in dev, but was committed yesterday. Sometimes the `encrypt` method was being passed values other than the password as the encryption key, leading to un-unlockable vaults. To find this, and avoid it for all time hereafter, I added several more steps to our oft-neglected integration test suite, which now fully initializes a vault, locks it, and unlocks it again, to make sure all of those steps definitely work always.
* Add integration tests for logging out and back inDan Finlay2016-12-011-1/+27
|
* Add more integration testsDan Finlay2016-12-011-0/+25
| | | | | | | | Integration tests now: - Scroll through terms - Accept terms - Confirm seed phrase - Verify account detail screen
* Made integration test create a first vaultDan Finlay2016-12-011-0/+22
|
* Fix integration test suiteDan Finlay2016-11-081-11/+3
|
* Remove debugger statement.Kevin Serrano2016-10-261-1/+0
|
* Phase out extra warning screen.Kevin Serrano2016-10-261-2/+1
|
* Began adding browser-native encryptor moduleDan Finlay2016-10-131-0/+25
Added new Qunit build process that will browserify the contents of `test/integration/lib` into the QUnit browser, allowing much more modular testing, including unit testing of our modules in our target browsers. Made a basic unit test file of this form for the new encryptor module, which fails miserably because I've only just begun to work with it. I've started with this blog post as a starting point, and will be adjusting it to our needs from there: http://qnimate.com/passphrase-based-encryption-using-web-cryptography-api/