Automated Testing Architecture

[cvarjao]

Re-architecture mobile-wallet-test-harness so that functional testing is more close to developer coding and definition of done. Perhaps some part stays at OWF, and BCW specific UI testing stays within BC wallet repository.

Acceptance Criteria

• Is it worth the effort since we have comprehensive component testing?
• Perhaps more lightweight on the the integration tests?
• Devs need a way to easily/quickly run locally
• Part of dev flow (maybe same repo)
• how to integrate with development/coding flow
• Test Accessibility labels
• How it renders in different devices/OS versions