feat(android/engine): Automated Android/embedded-web integration testing and logging
- Dominant language
- Pascal
- Stars
- 534
- Forks
- 143
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 113
Description
**Issue by [jahorton](https://github.com/jahorton)**
Would it be possible to develop a few automated tests on the KMEA side (base configuration) that can check a few basic assumptions about the embedded page? Having a quick check for basic properties (a proper OSK gets built, the keyboard is set properly, etc) would be nice for preventing a few issues that arose and slipped through to master. ~~and it shouldn’t be too difficult to do.~~
TODOs
- [ ] Implement non-CI test for testing KMEA's `setActiveKeyboard` equivalent
- [ ] (Post-research req't) Include KMW's recorder code for use as a keyboard-automation driver for testing. (Needed for using the Globe key to keyboard-swap)
- [ ] Convert non-CI tests to CI-compatible tests.
Contributor guide
Assessment
This issue has not been assessed yet.