Skip to content
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

Test duration time with console.log #2217

Closed
kaansan opened this issue Mar 15, 2018 · 2 comments
Closed

Test duration time with console.log #2217

kaansan opened this issue Mar 15, 2018 · 2 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: question The issue contains a question that won't be addressed.

Comments

@kaansan
Copy link

kaansan commented Mar 15, 2018

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

There is a durationMs with json reporter but I would like to see test durations on console.

What is the expected behavior?

I would like to see test durations on console with console.log

Test Name: {test name}
Duration: xxx seconds
@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: question The issue contains a question that won't be addressed. label Mar 16, 2018
@AlexanderMoskovkin
Copy link
Contributor

Hi @kaaanshady,

TestCafe built-in reporters don't output duration of each test but TestCafe allows to create a custom reporter that outputs test results in a required format. See the Reporter Plugin documentation section for details.

Additionally TestCafe allows to use multiple reporters in a single test run (see the --reporter option). You can output results from your custom reporter to the console and save the json report to the file.

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: question The issue contains a question that won't be addressed.
Projects
None yet
Development

No branches or pull requests

2 participants