Hello fellow coders! Today, Iโm excited to share my progress on the Recipe Detail feature for the app. ๐
What did I do? ๐ค
I adopted Test-Driven Development (TDD), a strategy that always keeps me confident about the stability of my code, especially when introducing new features or making changes.
Testing Dependencies ๐งช
The first step was to test the dependencies. In this case, the major dependency was the RecipeDetailFetcher, a crucial piece of the code responsible for fetching the specific details for each recipe. ๐ฅ
Testing the ViewModel ๐
After ensuring that the RecipeDetailFetcher was functioning perfectly, I moved on to test the RecipeDetailViewModel. I focused on three significant test cases:
testWhenStartFetchingDetails_RecipeDetailFetcherReceiveCorrectRecipe: This test made sure that the correct recipe is sent for fetching the details.testWhenFetchingSuccess_ViewModelDisplayCorrectRecipeDetail: This test confirmed that the ViewModel accurately displays the recipe details when the fetching is successful.testWhenFetchingFail_ViewModelDisplayCorrectError: This test verified that the ViewModel correctly displays an error message when the fetching fails.
Using the Dependencies Library ๐
To make testing easier and more efficient, I used the Dependencies library to stub the RecipeDetailFetcher. This allowed me to simulate different scenarios without making actual API calls, which sped up the testing process and made it more reliable. ๐
Wrapping Up ๐
By following these steps, I was able to confidently build and test the Recipe Detail feature, knowing that it works as expected in different scenarios. ๐ฅณ
You can check out the full code and tests on my GitHub repository. Feel free to browse through it, pull it down, and play around. Iโm always open to feedback and suggestions. ๐
Thanks for joining me on this journey! Stay tuned for more updates on this exciting project. Happy coding! ๐ป๐