-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stops after a failing test #394
Comments
@DanielMSchmidt I am not sure this is a bug. I think it's the intended behavior. |
@LeoNatan, I don´t think it's intended behavior. At least for me, I wanna now if besides any bug everything else is working or not. That's why makes sense for me testing everything and at the end show what worked and what didn't. |
Yes, I understand what you meant. I was just responding to @DanielMSchmidt adding the "bug" label. This could be an "enhancement" or something that we will not implement. For example, what should the expected behavior be if an app crashes between tests? Crashes are already difficult to handle—we don't handle them properly in Detox right now—what should the behavior be for the rest of the tests? I assume you don't relaunch your app before each test? Changing the existing behavior requires investigating all problems that could arise. |
@LeoNatan Sorry, I thought we already had something to handle this scenario. I removed the bug label. |
Got you. I used to test my app with Appium, and I'm trying to use detox due my company decided to use react native. With appium, in case of crashes between tests it restart the app and continue. I guess this is the expected, this way you can see if the problem is especifically in one testcase or with something else. In my user opinion, it's something to be implemented (I really need it... ) |
Let's keep the issue open for now. Let's see what @rotemmiz says. @DanielMSchmidt We may have. Awaiting mizmiz comment. 😉 |
@alissa-ferro this is out of Detox's scope. The test runner's job to decide if it should bail or continue to test the other tests in the suite. |
That´s perfect! Thanks! |
Hey!
When I have a failing test the other tests doesn't run. In my case, there are 4 tests but only 2 are executed.
Here are my verbose logs:
The text was updated successfully, but these errors were encountered: