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.

Sign up for GitHub

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

Jump to bottom

Better reporting in tests #28

Open
oggy22 opened this issue Apr 25, 2016 · 0 comments
Open

Better reporting in tests #28

oggy22 opened this issue Apr 25, 2016 · 0 comments
Assignees
@oggy22

Comments

@oggy22
Copy link
Owner

oggy22 commented Apr 25, 2016

Currently, many tests only assert without a good failure message. This is due to the fact that many classes don't have string/wstring converters. Write these converters and use them in the tests.
@oggy22 oggy22 self-assigned this Apr 27, 2016
oggy22 added a commit that referenced this issue Jul 17, 2017
@oggy22
Progress on #28, some reportings in tests decent
62b1c49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oggy22 oggy22

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oggy22