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

Print list of all failed tests. #1244

Closed
angelskieglazki opened this issue Oct 4, 2019 · 6 comments
Closed

Print list of all failed tests. #1244

angelskieglazki opened this issue Oct 4, 2019 · 6 comments

Comments

@angelskieglazki
Copy link

Hi, I’ve made a small patch that displays the list of all failed tests at the end. I think it would be useful. For example, my friend wrote about 400 tests and there’s no point in trying to find a failed test in the terminal log.

regards, max

@basvodde
Copy link
Member

basvodde commented Oct 5, 2019

Did he write 400 tests without running them?

@angelskieglazki
Copy link
Author

Did he write 400 tests without running them?

No :). Just now the code base of the project is changing very much

@basvodde
Copy link
Member

Ok, but if there are so much tests failing, then I would think you don't run them frequently enough. Personally I never needed a summary at the end, so I'm a bit surprised by the request.

I'll definitively not merge a feature that always gives a summary at the end as it would just produce more output that is most of the time not needed....

@angelskieglazki
Copy link
Author

@basvodde Hello, Bas. I added a flag for this functionality(-pse) so that it does not work by default as you would like. I remember your remark about the std::list container. What is the best way to replace it based on the guideline project? Write a template class or just make a dynamic array of strings in pure-c style?

Regards.

@basvodde
Copy link
Member

Unfortunately, also templates ought to be avoided, so you'll need to build your own list. You'd probably end up making a TestFailureList.

Also, there are no tests in the pull requests. We will not accept anything that doesn't have any test coverage and recommend people to actually test-drive their changed.

Other than these two, I have no comments on the PR so far.

@basvodde
Copy link
Member

Closing this issue as we have an open PR for the discussion related to this.

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

No branches or pull requests

2 participants