(Feature) Check that contract is deployed by requesting owner

[phahulin]

• What is it? (leave one option)

  • New (Feature) implementation

• What was the root cause of the problem originally / what feature was missing? If accidentally connected to wrong network, no warning is currently displayed, you can start using the DApp and receive various errors later.

• How does this pull request solve it (in broad terms)? Check code property of account at ContractOutput.address (should be not empty). Get owner of that contract (should be not empty).

• Does it close any open issues? Related to https://github.com/poanetwork/poa-popa/issues/52

• Quick checklist

  • [ ] eslint shows no errors

    cd web-dapp
    eslint .

  • [X] docs were updated where necessary OR they don't need to be updated
  • [X] tests were updated where necessary OR they don't need to be updated

[phahulin]

@fvictorio please advise how to resolve ci error:

 FAIL  src/components/App.test.js
  ● Test suite failed to run
    Cannot find module '../contract-output' from 'App.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:179:17)
      at Object.<anonymous> (src/components/App.js:9:49)

On my local machine where I have contract-output.json it passes, but I'm not sure how to do it here, tried to use mocked version from test/server/_utils/mock-contract-output.json but no luck.

Can we just tell travis to install and run ganache-cli and deploy the contract on test network?

[coveralls]

Pull Request Test Coverage Report for Build 121

• 2 of 28 (7.14%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.6%) to 30.351%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
web-dapp/src/components/App.js	2	28	7.14%
<!--	Total:	2	28	7.14%	-->

Totals
Change from base Build 120:	-0.6%
Covered Lines:	328
Relevant Lines:	1023

---

💛 - Coveralls