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.

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

Use Full Dagger Graph for unit tests #467

Merged
merged 12 commits into from
Apr 8, 2021
Merged

Conversation

jraska
Copy link
Owner

@jraska jraska commented Apr 8, 2021

  • Fake Modules created - some boilerplate, but this should be one time effort per module.
  • ViewModel is tested with real dependencies, only network is mocked.
  • Items are tested against full domain object - in case the domain changes, test is forced to be updated.
  • Fakes with recording used everywhere - no Mockito

@jraska jraska force-pushed the use-full-dagger-for-unit-tests branch from 282ae5c to 5c8c8ed Compare April 8, 2021 22:30
@jraska jraska enabled auto-merge (squash) April 8, 2021 22:41
@sonarcloud
Copy link

sonarcloud bot commented Apr 8, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 6 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@jraska jraska merged commit 1f22879 into master Apr 8, 2021
@jraska jraska deleted the use-full-dagger-for-unit-tests branch April 8, 2021 23:55
@github-actions
Copy link
Contributor

github-actions bot commented Apr 9, 2021

This PR was released in 0.27.0. 🚀

@github-actions github-actions bot added this to the 0.27.0 milestone Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant