tag:blogger.com,1999:blog-8619555037506461466.post4142383996164976113..comments2018-08-18T07:47:45.858+02:00Comments on Garajeando: Solving the Tire Pressure Monitoring System exercise (IV)Manuel Riverohttp://www.blogger.com/profile/03913204576202587259noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8619555037506461466.post-54439579639323958552016-02-09T12:03:22.572+01:002016-02-09T12:03:22.572+01:00Thanks for the explanation!Thanks for the explanation!Anonymoushttps://www.blogger.com/profile/17457371721932297509noreply@blogger.comtag:blogger.com,1999:blog-8619555037506461466.post-27561632751509740892016-02-09T11:17:59.646+01:002016-02-09T11:17:59.646+01:00Thanks!
SafetyRange is not mocked because it'...Thanks!<br /><br />SafetyRange is not mocked because it's a value object.<br /><br />This post talks about things you shouldn't try to mock:<br />Test Smell: Everything is mocked<br />http://bit.ly/1QSs0PQManuel Riverohttps://www.blogger.com/profile/03913204576202587259noreply@blogger.comtag:blogger.com,1999:blog-8619555037506461466.post-55825925124428119632016-02-09T10:46:45.966+01:002016-02-09T10:46:45.966+01:00Great article! I have one question though.
After ...Great article! I have one question though.<br /><br />After refactoring you now have a call to the class SafetyRange<br />safetyRange.isNotWithin(value)<br /><br />Why isn't SafetyRange mocked in this example? I always thought you shouldn't call "real class" in a unit test... Just curious.<br /><br /> <br /><br />Anonymoushttps://www.blogger.com/profile/17457371721932297509noreply@blogger.com