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

Logging of Test execution in QTTestDriver verbose mode #304

Open
kreuzberger opened this issue Jul 30, 2024 · 2 comments
Open

Logging of Test execution in QTTestDriver verbose mode #304

kreuzberger opened this issue Jul 30, 2024 · 2 comments
Labels

Comments

@kreuzberger
Copy link
Contributor

kreuzberger commented Jul 30, 2024

🤔 What's the problem you're trying to solve?

Currently if the steps run without any problems, the output from the test could not be logged or seen. The output is stored in a file that is removed after test and does not contain helpful information on success cause no loglevel is provided to the test

✨ What's your proposed solution?

The verbose flag or another flag should be provided to the TestDriver implementation.
The testdriver should then configure the tests with the appropriate, driver specific loglevels.
The output of the test could be

  • provided as "description" as part of the InvokeResult::success() like for the other Resulttypes
  • the description should be logged out in case of the verbose flag enabled.

⛏ Have you considered any alternatives or workarounds?

The logging could be done in the steps implementation by NOT using the QT macros qInfo() or by providing an messagehandler for this. Long text short: logging to stderr is possible and output from stderr is shown. This could also a way to enable logging. But in failure cases the context of these logs and the steps executions do not match. This might not be helpfull.

📚 Any additional context?

No response

@ursfassler
Copy link
Contributor

This sounds reasonable.
Do you have a concrete use case where you need this? It is to better understand how it will be used.

@kreuzberger
Copy link
Contributor Author

  • During development of tests i want to see whats going on without always to fail the tests.
  • For review / explanation in team i want to show the test execution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants