Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Asserts for CharSequence contents
See original GitHub issueA lot of APIs in Android deal with CharSequence. And using assertEquals() with CharSequence arguments is cumbersome and unstable. One has to reproduce the exact same type which might change later.
And sometimes it just does not work (e.g. StringBuilder uses default Object.equals() implementation).
Therefore I would suggest to add new methods like
assertContentEquals(CharSequence expected, CharSequence actual)
that would compare just the content, irregardless of the type it’s been wrapped into.
(Pull request #949 was trying to do that with generic assertEquals() which is indeed questionable)
I can create a pull request if you find this proposal reasonable.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@joseph-mccarthy GitHub apparently only lets you assign issues to someone on the project’s team. But we almost never assign issues anyway. Feel free to submit a pull request after reading https://github.com/junit-team/junit4/blob/master/CONTRIBUTING.md
@kcooney I am assuming that @joseph-mccarthy is no longer working on this and I’ve opened a PR with implementation.