<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Uncategorized on Dhaval Shah</title><link>https://www.dhaval-shah.com/categories/uncategorized/</link><description>Recent content in Uncategorized on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 16 Jan 2017 18:14:52 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/categories/uncategorized/index.xml" rel="self" type="application/rss+xml"/><item><title>Anatomy of Test Driven Development – Part 2</title><link>https://www.dhaval-shah.com/anatomy-of-test-driven-development-part-2/</link><pubDate>Mon, 16 Jan 2017 18:14:52 +0000</pubDate><guid>https://www.dhaval-shah.com/anatomy-of-test-driven-development-part-2/</guid><description>This is the concluding blog of 2 part series on 'Anatomy of Test Driven Development'. Continuing from where we left in first part of this series, this will mainly talk about 'How' part of TDD along with its avatars.
How to do TDD
We start with a Test. To get this to work we need to frame the test. We need to make sure that there is enough code in place to make it compile or to make it to work and not throw up run time error.</description></item></channel></rss>