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

Consider wording changes for some assertion failure messages #76

Closed
GoogleCodeExporter opened this issue Jun 21, 2015 · 2 comments
Closed

Consider wording changes for some assertion failure messages #76

GoogleCodeExporter opened this issue Jun 21, 2015 · 2 comments
Labels
auto-migrated Milestone-Release2.1.1 Priority-Low Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

For example, I don't like all the "got" verbiage, and the following is a tongue 
twister: "Got the expected exception, but the exception assertion failed"

Original issue reported on code.google.com by stephen....@gmail.com on 14 Dec 2011 at 5:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-Release2.1.1 Priority-Low Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter