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

丰富单测报错 #5305

Closed
TOMO-CAT opened this issue Jul 4, 2024 · 4 comments
Closed

丰富单测报错 #5305

TOMO-CAT opened this issue Jul 4, 2024 · 4 comments

Comments

@TOMO-CAT
Copy link

TOMO-CAT commented Jul 4, 2024

你在什么场景下需要该功能?

如果单测过多的话,需要往前翻看哪个单测挂了以及查看单测的日志输出。
希望可以将挂掉的单测日志保存在一个文件,以及在跑完单测后输出控制台查看哪些单测过了哪些单测没过。

描述可能的解决方案

类似 bazel 单测跑完后的结果:
image

描述你认为的候选方案

No response

其他信息

No response

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: Rich single test error reporting

In what scenario do you need this function?

If there are too many single tests, you need to look forward to see which single test failed and check the log output of the single test.
I hope that I can save the failed single test log in a file, and after running the single test, output the console to see which single tests passed and which failed.

Describe possible solutions

Similar to the results after running the bazel single test:
image

Describe your alternatives

No response

other information

No response

@TOMO-CAT
Copy link
Author

TOMO-CAT commented Jul 6, 2024

执行 xmake test -v 的时候能不能和 xmake run 一样同步输出日志,如果这个和丰富单测报错允许的话我自己能提个 PR 吗就不耽误你们的开发了

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


When executing xmake test -v, can the log be output synchronously like xmake run? If this and rich single test error reporting are allowed, can I submit a PR myself so as not to delay your development?

@waruqi
Copy link
Member

waruqi commented Jul 25, 2024

#5387

@waruqi waruqi added this to the v2.9.4 milestone Jul 25, 2024
@waruqi waruqi closed this as completed Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants