feature: add reload method to easily reset app state during tests #114
Conversation
| `--config=${jestConfigPath}`, | ||
| `--roots=${cwd}`, | ||
| '--runInBand', | ||
| `--globals='${JSON.stringify({ OWL_CLI_ARGS: args })}'`, |
There was a problem hiding this comment.
Adding the Owl config as a global variable, so that it can be accessed from the refresh method during the test.
There was a problem hiding this comment.
I'm also considering adding a __OWL__ or similar global here so that it can easily be used in the app to swap to using mock data etc during tests.
A good use case would be to show a Story Book type screen during Owl tests only, so that all components can be easily tested.
| import { adbInstall, adbLaunch } from '../utils/adb'; | ||
| import { | ||
| xcrunInstall, | ||
| xcrunLaunch, | ||
| xcrunRestore, | ||
| xcrunStatusBar, | ||
| xcrunUi, | ||
| } from '../utils/xcrun'; |
There was a problem hiding this comment.
All of the separate build and run steps that use either ADB or xcrun have been refactored out into separate util functions. This is so that the same functions can be easily reused at other times, such as using xcrunLaunch or adbLaunch during testing as part of the reload method.
robwalkerco
changed the title
This PR adds a new
reloadmethod that terminates then relaunches the app, so that it's easier to split tests up into separate batches that each can start from a fresh app state.