Error logs are not clear

[imtiazhossain]

When running cucumber tests in webdriverio, the error logs do not tell me exactly what is wrong with the test. I just see "undefined"

F․․

0 passing (24.70s) 2 pending 1 failing

1) Verify test undefined running chrome undefined

I'd like to see what is undefined.

[christian-bromann]

@imtiazhossain how did that test fail? It seems that it didn't even start at all. Please provide more debug logs from Selenium and WebdriverIO

[imtiazhossain]

@christian-bromann thanks for the quick reply. It failed because a selector couldn't be found but I had no idea what selector or which line until I searched for it.

[christian-bromann]

Can you please provide a minimal reproducible example?

[imtiazhossain]

The issue is that I'm not seeing any of the logs that cucumber provides using the 'dot' reporter. I don't see my steps or anything. I think it's because it shows dot reporting by default. Is there a way to turn this off? The console shouldn't just say 'undefined'. It should say what is undefined. Thanks

[christian-bromann]

It should say what is undefined.

That is right but without having any code I can't guess why this is. Feel free to do some debugging 😉

[imtiazhossain]

The code runs but when it fails, it doesn't tell me anything useful in the console. Attached is a screenshot. Thanks

[christian-bromann]

What do your Selenium logs say?

[Kignuf]

Hello, I just wanted to let you know I am having the same issue from time to time. No 100% reproducible scenario for the moment but if I figure it out I'll get back to this thread.

I'm using appium (android). When it occurs it's bound to a failure from appium. Running the exact same test immediately afterwards usually works. So it's not an error in the test but an error in appium & an error in cucumber-wdio.

[christian-bromann]

Closing due to inactivity

[Kignuf]

This is fixed by https://github.com/webdriverio/wdio-cucumber-framework/pull/59