-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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.
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
Extend testing frameworks #99
Comments
Agreed @Brave-Warrior. This has been on my backlog for a while as the landscape has certainly changed since the initial version of this document. |
As a brief summary of my thoughts how to write tests:
@tomaszpolanski might have some input here too. |
When using Rx and "scheduled" observable, either inject schedulers or something that provides them. |
@peter-tackage agree with your points. But would extend the following items with the links to appropriate resources or detailed description:
add link for Mockito; the recommendations how to mock objects and the check behaviour in the better/best way
Link to AssertJ would be good and what are the advantages of that
not clear enough The other points are quite clear and could be added to the best practices. |
@tomaszpolanski Agreed. Testing Rx is probably worth it's own section. |
@Brave-Warrior I'll be progressing the testing section update under #114 |
Would be nice to have a section with best practices for using unit testing frameworks (JUnit, Mockito)
The text was updated successfully, but these errors were encountered: