<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.testingreflections.com">
<channel>
 <title>Phil Kirkham's blog</title>
 <link>http://www.testingreflections.com/blog/1577</link>
 <description></description>
 <language>en</language>
<item>
 <title>5 Questions For Antony Marcano</title>
 <link>http://www.testingreflections.com/node/view/7884</link>
 <description>I've recently been emailing 5 questions to some of the test blog authors out there. &lt;br /&gt;
One of them was the owner of this very site, &lt;b&gt;Antony Marcano&lt;/b&gt;, so if you'd like to read his answers which give some insight and history not just of himself but also of testingReflections then read on &lt;a href="http://expectedresults.blogspot.com/2009/02/5-questions-for-antony-marcano.html"&gt;here&lt;/a&gt;</description>
<pubDate>Thu, 19 Feb 2009 09:52:31 +0000</pubDate></item>
<item>
 <title>Totally Test Infected</title>
 <link>http://www.testingreflections.com/node/view/4656</link>
 <description>11 months on from my &lt;A href= "http://www.testingreflections.com/node/view/3146"&gt;first blog entry&lt;/a&gt; and the time of year that is traditionally used to look back and (test) reflect, where am I now ?&lt;br /&gt;
Sitting with the test team, that's where - thats what I call getting test infected.&lt;br /&gt;
&lt;br /&gt;
Though it took my boss all year to convince the board to allow a developer to switch roles to being a tester. So that means one of my goals for next year is glaringly obvious - educate the board into the value of testing and get them to realise that the programmers should be doing testing anyway.</description>
<pubDate>Sat, 02 Dec 2006 11:00:24 +0000</pubDate></item>
<item>
 <title>Eating an Elephant</title>
 <link>http://www.testingreflections.com/node/view/3222</link>
 <description>And so it starts - VSTE now installed on my machine and starting to explore what it offers. All the right words seem to be there - unit tests, code coverage, load testing, manual tests. Just the fact that they are there and people are discussing about how to use them is a giant step in the right direction.&lt;br /&gt;
&lt;br /&gt;
So it was with a mixture of excitment and nerves that I went over to a developers desk as he proudly showed me the first unit tests he'd written</description>
<pubDate>Thu, 09 Feb 2006 08:43:36 +0000</pubDate></item>
<item>
 <title>The Good Old Ways ?</title>
 <link>http://www.testingreflections.com/node/view/3169</link>
 <description>Here's the EXE now bash away at it and see if you can make it crash.&lt;br /&gt;
If you can't then ship it.&lt;br /&gt;
So much easier than having to think about testing in all it's flavours and methods.</description>
<pubDate>Thu, 26 Jan 2006 17:44:28 +0000</pubDate></item>
<item>
 <title>New to testing - Information Overload</title>
 <link>http://www.testingreflections.com/node/view/3146</link>
 <description>Finally, after a year of pressurising management, the small company I work for is ready to start with some proper test processes and procedures. At the same time there is also a push from the developers to try out an agile approach and use SCRUM for the new projects that are planned to happen. A developer who wants to move into testing could be very very busy....</description>
<pubDate>Thu, 19 Jan 2006 11:45:19 +0000</pubDate></item>
</channel>
</rss>

