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

fix assert.Equal to be (expected, actual) order #509

Closed
geek opened this issue Sep 19, 2017 · 0 comments
Closed

fix assert.Equal to be (expected, actual) order #509

geek opened this issue Sep 19, 2017 · 0 comments
Labels
refactor

Comments

@geek
Copy link
Contributor

geek commented Sep 19, 2017

The tests need to be reviewed and updated to make sure they follow the assert.Equal(t, expected, actual) interface, I've seen many that are (actual, expected)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jwreagor @geek