Testcafe: More verbose output about actions and assertions

[miherlosev]

https://stackoverflow.com/questions/56932508/how-to-be-more-verbose-on-tests
https://stackoverflow.com/questions/56980542/testcafe-display-steps-while-running-tests

It will be useful if TestCafe provides more info about executed steps. Example:

-------------------------------------------------------------------------
VISIT: http://example.com
TYPE: 'username' in #UserName
CLICK: 'submit' button
-------------------------------------------------------------------------

[joywave]

This would be nice to have

[Raynos]

I'd love this too, especially with timing information.

[eugene-tkachenko]

Can confirm that it would relieve lives of developers for sure.

[leob]

This is not just "nice", this would be an absolute lifesaver, which would (in many scenarios) make all the difference. Is there really not an option already which does just this? So, indeed, simply the ability to have the executed steps printed to the terminal (console). That would make it like a dozen times easier to know what's going, on and to troubleshoot things.

[Raynos]

npm i testcafe-reporter-spec-time -D
./node_modules/.bin/testcafe -r spec-time chrome:headless ./tests

This gives you timing granularity.

Alternatively there's a DEBUG flag you can set to get testcafe to output everything

DEBUG=testcafe:* testcafe

This will give you all the messages it sends between main process and browser process.

[leob]

Thanks!

I've tried the spec-time reporter - but, unless I'm mistaken, that doesn't address my problem - it's not printing what's going on, as it happens, while the test is running - it just prints the results after the test is finished.

I've tried DEBUG=testcafe:* and yes, that sort of achieves what I was looking for, but it's way way way too verbose, you then need to sift through a huge amount of cruft to see what's going on, that's virtually impossible.

So, yes a DEBUG=testcafe:* but much more concise, something along the lines of what @miherlosev was describing would be perfect.

It could be me, but I would say that this might be the #1 "game changer" feature which many TestCafe users are secretly craving for ;)

[Raynos]

I'd like to see a shortened version of DEBUG=testcafe:* as well with what actions took place, what selectors / assertions took place and an option to show more or less.