You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
Hello, I have a question about the end of the tests : usually, I have at the end a little summary telling me how many tests have passed and failed, like this :
==================================================================
Number of specs: 2
10 passing (65.20s)
2 failing
1) should have failed in purpose:
expected false to be true
running chrome (v64)
running safari
But when I have a problem on a device (as example, I run a test on Android and the devices has a problem during only 1 spec and don't play it), so 1 spec is not played (but the 9 others are well played), I don’t have this summary at the end
I just have
==================================================================
Number of specs: 10
So because of this only specs not played, I can't see how many Passed or Failed I've got.
I see that if I add
Hello, I have a question about the end of the tests : usually, I have at the end a little summary telling me how many tests have passed and failed, like this :
But when I have a problem on a device (as example, I run a test on Android and the devices has a problem during only 1 spec and don't play it), so 1 spec is not played (but the 9 others are well played), I don’t have this summary at the end
I just have
So because of this only specs not played, I can't see how many Passed or Failed I've got.
I see that if I add
just before this final line : https://github.com/webdriverio-boneyard/wdio-spec-reporter/blob/master/lib/reporter.js#L327 I can have my report about the 9 specs played and it's perfect because I don't have to scroll up and read everything to see if I've got failure because of this spec not played.
So is they're a better solution to have the report displayed ?
Thanks a lot :)
The text was updated successfully, but these errors were encountered: