﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Jeremy Gray commented on No testing, no software</title><description>As I become more and more TDD/BDD-infected I too am finding that all but my tiniest little spike efforts almost always go *-driven rather than me just hacking around. I just get this strange, creepy feeling in my stomach when I start coding without at least some test/spec code already written. :)
</description><link>http://ayende.com/3452/no-testing-no-software#comment2</link><guid>http://ayende.com/3452/no-testing-no-software#comment2</guid><pubDate>Wed, 06 Aug 2008 20:40:05 GMT</pubDate></item><item><title>Markus Zywitza commented on No testing, no software</title><description>I didn't used console projects for a long time. Since I started using UnitTests regularly, I create a testproject (dll) instead, writing the subject under test directly into the test project.
  
So, instead of testing with F5, I rather use TDD.Net (CTRL-R, CTRL-T and CTRL-R, CTRL-D for debugging).
  
When I finished exploring, I start over in new projects and leave the exploration project as a reference in the solution.
</description><link>http://ayende.com/3452/no-testing-no-software#comment1</link><guid>http://ayende.com/3452/no-testing-no-software#comment1</guid><pubDate>Sun, 27 Jul 2008 05:45:10 GMT</pubDate></item></channel></rss>