What's Changed
This release brings a new device allocation lifecycle (#4173, @noomorph) – the device management moved to the parent process (as opposed to every child (worker) process before). This is a backwards-compatible change for most of the users, but we recommend custom Detox driver maintainers to check for any issues (cc @awinograd).
- Fixed
-u, --cleanupoption. For example, in Jest, devices used to shut down prematurely after each test file. Now they will only shut down after the entire test session (#2894) - [Genymotion SaaS] The
-R, --retriesoption functions correctly after initial boot failures (#3655). - Fixed race conditions when running multiple
detox test...commands at once (#3573)
Technical changes
detox reset-lock-filecommand is no longer needed for 99.9% of cases- All the device registries (lock files) have been reduce to a single one
- The cookie object issued by the allocation driver must be a plain serializable object (NB @awinograd), not an instance of a class
Full Changelog: 20.12.2...20.13.0