establish e2e testing strategy

[jbibla]

• The critical functionalities are tested E2E via some automated browser tests
• break up e2e into component tickets

[faboweb]

Most UI functionality is tested via unit tests.

What is not covered:

• test if app actually starts
  • included by following tests
• test if app builds and runs
  • test if the build succeeds is running
  • done in Test build executables #410
• test if communicating with the network actually works
  • @mappum how about a TEST_BOT account we persist in the genesis. we then use this account to send some "test_bot_coins" to himself on the actual network?

[faboweb]

Investigating on the e2e tests Matt wrote, I see, that those already cover core topics. I will try to bring those to the latest gaia and UI.

[mappum]

how about a TEST_BOT account we persist in the genesis. we then use this account to send some "test_bot_coins" to himself on the actual network?

I like this idea. This will be easiest with a local testnet, and it will be nice to add other tests here such as delegating.

We should be able to use Spectron to automate the app, I had a good experience with that on the old e2e tests.

[faboweb]

Currently blocked on the Linux package of Gaia not being properly installable