Gray box end-to-end testing and automation framework for mobile apps
MIT License
Bot releases are visible (Hide)
Published by asafkorem over 2 years ago
Published by asafkorem over 2 years ago
⚠️ This version was not properly published to npm (broken package). Please use 19.5.1, instead.
Published by d4vidi over 2 years ago
⚠️ It appears this version was not properly published to npm
(broken package). Please use 19.5.1
, instead.
spawn
instead of exec
(#3224, @d4vidi)Full Changelog: https://github.com/wix/Detox/compare/19.4.5...19.5.0
Published by noomorph over 2 years ago
Full Changelog: https://github.com/wix/Detox/compare/19.4.4...19.4.5
Full Changelog: https://github.com/wix/Detox/compare/19.4.3...19.4.4
Published by asafkorem over 2 years ago
simctl terminate
error when app is not running (#3205, @asafkorem).signal 11
crash when Firebase-Performance is integrated, with a designated fix, introduced in GoogleUtilities v7.7.0 (#3167, @asafkorem) – see also: firebase/firebase-ios-sdk#9083.Published by jonathanmos almost 3 years ago
Same as 19.4.0
Published by jonathanmos almost 3 years ago
Official React Native 0.66.x
and Android 12 support! 🎆 🎊
This was a bit of a tricky one, due to this newly introduced, hidden RN bug - https://github.com/facebook/react-native/issues/32594, which we've managed to work-around.
Here's the scope of things:
1.2.0
to 1.4.0
(#2817, @jonathanmos). Note that this would make some of your DetoxTest.java
code generate deprecation warnings. We are aware of it and are planning to address that in Detox 20.0.0
.Also, introduced:
signal 11
crashes when Firebase-Performance is integrated (#3135, @asafkorem 🚀 )Published by d4vidi almost 3 years ago
Fixes:
19.0.0
: Update demo-plugin example to fit Detox v19 (#3082, @d4vidi)Published by d4vidi almost 3 years ago
await
statements on asynchronous Detox APIs. That’s why you might see a new error like this:
FAILED
DetoxRuntimeError: The pending request \#246 ("invoke") has been rejected due to the following error:
Detox has detected multiple interactions taking place simultaneously. Have you forgotten to apply an await over one of the Detox actions in your test code?
That should help you find forgotten await
s in your code that are a potential reason for flakiness in E2E tests. You’ll need to find those places and apply trivial fixes like shown below:
await screenDriver.performSomeAction();
- expect(screenDriver.get.myElement()).toBeNotVisible();
+ await expect(screenDriver.get.myElement()).toBeNotVisible();
element(...).getAttributes()
(#3009, @princefishthrower, @noomorph)