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

need EXPECT_THAT and matchers from googlemock #191

Open
GoogleCodeExporter opened this issue Jul 31, 2015 · 2 comments
Open

need EXPECT_THAT and matchers from googlemock #191

GoogleCodeExporter opened this issue Jul 31, 2015 · 2 comments
Labels
auto-migrated OpSys-All Priority-High Type-Enhancement Usability

Comments

@GoogleCodeExporter
Copy link 

These are generally useful constructs.  We should move them from googlemock.

Assigning to Vlad, who expressed interest in moving the googlemock
value-printer to googletest before.

Original issue reported on code.google.com by [email protected] on 2 Sep 2009 at 6:58
@GoogleCodeExporter
Copy link
Author 

Increased priority based on user request and potential impact.

Original comment by [email protected] on 4 Jan 2010 at 5:05

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 27 Sep 2010 at 7:10

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 OpSys-All Priority-High Type-Enhancement Usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter