👨🏻‍💻 Puppeteer user acceptance tests

[zmilonas]

[zmilonas]

@subdavis I will for sure do that when I broaden the test cases and agree on the final naming and path scheme.

For now you can play around using

yarn install
node_modules/.bin/mocha tests/integration/integration.js

That's it :)

[zmilonas]

Let's start from here. These test pass right now. I have a plan to create an end to end sample database unlock search and autofill test later but I might not get to it soon enough. Will have to think about adding qa html classes as well to stuff. @subdavis please review and run the tests on your machine :) Then we can add it to travis configuration (after that's merged as well)

[subdavis]

might take a while to get to the travis PR. Let's merge this first. I'll review this weekend

[zmilonas]

Thank you, I might also rename it first, Do you agree these will be Chrome user acceptance tests So I would put them under tests/uat/chrome.js as I add more tests I'll probably split these UATs into view, database, storageProviders and so on under uat

[subdavis]

I still don't know how this works. After generating a build, I get a message about failing to load options.html.

[zmilonas]

I think it might be related to the extension ID I hardcoded in the test. I have look into getting the installed extension ID again. I thought the web store one is going to be persistent but that's a really bad assumption 😂