<?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>Antony Marcano's blog</title>
 <link>http://www.testingreflections.com/blog/2</link>
 <description></description>
 <language>en</language>
<item>
 <title>FitNesse ships with dotnet 1.1...  still??!!</title>
 <link>http://www.testingreflections.com/node/view/7329</link>
 <description>&lt;p&gt;Firstly, my thanks to &lt;a href="http://gojko.net/"&gt;Gojko Adzic&lt;/a&gt; for giving such a rapid response on the FitNesse mailing list to help me solve the problem I encountered getting my .NET assemblies loaded in FitNesse .NET...&lt;/p&gt;

&lt;p&gt;After at least 2 years of doing absolutely no .NET work, I started working with a .NET team this week, helping them to use FitNesse.&lt;/p&gt;

&lt;p&gt;Trying to run my test for the first time, the FitServer.exe just wasn't finding my assembly... HelloFitNesse.dll&lt;/p&gt;</description>
<pubDate>Wed, 03 Sep 2008 06:26:47 -0500</pubDate></item>
<item>
 <title>Free evening talk: Understanding Qa/Testing On Agile Projects</title>
 <link>http://www.testingreflections.com/node/view/7313</link>
 <description>&lt;p&gt;I'll be giving a free evening public talk in Clerkenwell, London for SkillsMatter on 8th September at 18:30pm. The talk is applicable to anyone on an agile team or running agile projects...&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Testing is an integral and prominent aspect of agile development, however, new teams form and existing teams prevail with uncertainty about how testers fit into the process. Even those projects that don’t have testers dedicated to them can still feel there is a void in how they ensure that they are building the right product and building the product right.&lt;/p&gt;</description>
<pubDate>Tue, 26 Aug 2008 10:07:37 -0500</pubDate></item>
<item>
 <title>Tester-developer/developer-tester... transitional like ye-olde analyst-programmer</title>
 <link>http://www.testingreflections.com/node/view/7280</link>
 <description>&lt;p&gt;Cross-functional teams are growing in popularity, influenced in no small part by the growth in adoption of agile values and the methodologies that support them.&lt;/p&gt;

&lt;p&gt;Whether it's a side effect of getting developers and testers working more closely or due to the undulating skills demands from iteration to iteration, each team-member is increasingly expected to have more diverse skills. Furthermore, Test Driven Development increases the need for developers to know more about testing; automated acceptance tests as part of Acceptance Test Driven Development written in the same language as the product increases the need for testers to know about programming.&lt;/p&gt;</description>
<pubDate>Tue, 12 Aug 2008 07:56:06 -0500</pubDate></item>
<item>
 <title>public class TeamMember implements ITestSoftware, IWriteCode, IDevelopProducts... and a special forces twist...</title>
 <link>http://www.testingreflections.com/node/view/7278</link>
 <description>&lt;p&gt;No, this isn't on the same topic as &lt;a href="http://www.testingreflections.com/node/view/7234"&gt;my previous post on Udi Dahan's interface naming style&lt;/a&gt;. But, I have taken inspiration from it as I've been trying to find a way to communicate a people issue.&lt;/p&gt;

&lt;p&gt;In that post, I was illustrating a point that Udi had made about naming interfaces not based on what they are but what they do... based on their roles...&lt;/p&gt;</description>
<pubDate>Mon, 11 Aug 2008 19:24:52 -0500</pubDate></item>
<item>
 <title>ISubmitBlogPosts - a nice twist on Apps Hungarian Notation for Interfaces...</title>
 <link>http://www.testingreflections.com/node/view/7234</link>
 <description>&lt;p&gt;I've been pairing with &lt;a href="http://andyp-tw.blogspot.com/"&gt;Andy Palmer&lt;/a&gt; over this last week. I have to say it's been a lot of fun... and I think we've learned a lot from the experience. One of the things I learned from Andy this week was an innovative use of Hungarian notation for interfaces... Andy told me about &lt;a href="http://www.udidahan.com/"&gt;Udi Dahan's&lt;/a&gt; presentation on &lt;a href="http://cid-c8ad44874742a74d.skydrive.live.com/self.aspx/Blog/Intentions%20and%20Interfaces.pdf"&gt;intentions and interfaces (PDF)&lt;/a&gt;&lt;/p&gt;</description>
<pubDate>Thu, 14 Aug 2008 09:04:37 -0500</pubDate></item>
<item>
 <title>The Telephone Game...</title>
 <link>http://www.testingreflections.com/node/view/7232</link>
 <description>&lt;p&gt;In an &lt;a href="http://www.testingreflections.com/node/view/6660"&gt;earlier post, I mentioned Boehm's distinction between 'verification' and 'validation'&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Verification - Am I building the product &lt;i&gt;RIGHT&lt;/i&gt;?&lt;/p&gt;
&lt;p&gt;Validation   - Am I building the &lt;i&gt;RIGHT&lt;/i&gt; product?&lt;/p&gt;
&lt;p&gt;&lt;i&gt;-Boehm, Software Engineering Economics&lt;/i&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;As I was writing an article to appear in the October 2008 issue of &lt;a href="http://www.stickyminds.com/BetterSoftware/magazine.asp"&gt;Better Software Magazine&lt;/a&gt; I arrived at a better way of getting my point across...&lt;/p&gt;</description>
<pubDate>Sun, 10 Aug 2008 05:03:53 -0500</pubDate></item>
<item>
 <title>A test is "an example of the rule in practice", but...</title>
 <link>http://www.testingreflections.com/node/view/7216</link>
 <description>&lt;p&gt;In &lt;a href="http://parlezuml.com/blog/"&gt;Jason Gorman's&lt;/a&gt; post called &lt;a href="http://parlezuml.com/blog/?postid=671"&gt;Tests Are Instances Of Rules&lt;/a&gt; he says:&lt;/p&gt;


&lt;blockquote&gt;
&lt;p&gt;In test-driven development, we use tests as executable specifications of what is required of the software we create.&lt;/p&gt;

&lt;p&gt;For this to work effectively, our tests have to convey the underlying intent. And this requires us to ponder the relationship between a test and a specification.&lt;/p&gt;</description>
<pubDate>Wed, 06 Aug 2008 17:23:49 -0500</pubDate></item>
<item>
 <title>How nice it is to see...</title>
 <link>http://www.testingreflections.com/node/view/7208</link>
 <description>&lt;p&gt;I can't tell you how satisfying it is to see the fruits of my labours! I had a particularly proud moment when I read &lt;a href="http://www.bbc.co.uk/blogs/bbcilabs/2008/07/32_burndowns.html"&gt;32 Burndowns by Rob Hardy&lt;/a&gt; on the &lt;a href="http://www.bbc.co.uk/blogs/bbcilabs/"&gt;BBCi Labs blog&lt;/a&gt;... The rich collection of example burn-downs tell 32 different stories... and Rob's summary of how these projects work is dramatically different to the one he might have told only 2 years ago... but for me the gratifying aspect of this is seeing the ongoing growth in their development and understanding of what they do, how they do it and why they do it that way...&lt;/p&gt;</description>
<pubDate>Sun, 03 Aug 2008 07:02:54 -0500</pubDate></item>
<item>
 <title>QA/Testing (Again)</title>
 <link>http://www.testingreflections.com/node/view/7192</link>
 <description>&lt;p&gt;Software is about the only industry that lumps testing and QA under one banner. It's one of those things where common misuse of a term results in the community changing it's meaning... this happens in mainstream language all the time. &lt;/p&gt; 

&lt;p&gt;Testing something is actually more analogous to quality control or, QC. QA is more concerned with the process - collecting information about the performance of the process in order to determine if we are 'assuring' (or more realistically increasing the probability of) quality. Statistical information about problems found in the product (during quality control) is just one of many pieces of info useful to someone concerned with QA (which really should be the whole project team)&lt;/p&gt;</description>
<pubDate>Sat, 26 Jul 2008 13:21:55 -0500</pubDate></item>
<item>
 <title>Hitting the nail on the head...</title>
 <link>http://www.testingreflections.com/node/view/7122</link>
 <description>&lt;p&gt;For a while, I've been trying to describe how I work... how I coach teams... Or at least how I have been for a while now anyway. I've said things like "I focus on values not practices" or "I help people understand what they want to achieve then help them find ways to achieve it"... or "I help teams ask questions of themselves that, with the benefit of hindsight, I would have asked myself". However, after reading &lt;a href="http://parlezuml.com/blog/?postid=655"&gt;Jason Gorman's post&lt;/a&gt; I realised that, completely by accident, I was doing much the same thing. Jason says:&lt;/p&gt;

&lt;blockquote&gt;
Instead, I finally admitted that my real job is to persuade people that they want to learn. And not in any bulls**t manipulative way. I've focused the largest part of my effort on being a catalyst to help recharge people's interest and passion for what they're doing.
&lt;/blockquote&gt;</description>
<pubDate>Wed, 25 Jun 2008 05:06:20 -0500</pubDate></item>
<item>
 <title>STAREast Interview now available as a Podcast...</title>
 <link>http://www.testingreflections.com/node/view/7058</link>
 <description>For anyone interested, I was interviewed after giving my "Behind every bug is a story" tutorial at STAREast.

This &lt;a href="http://www.stickyminds.com/ControlImages/StickyMinds/Image/Podcast/Audio/SE08Live_Marcano.mp3"&gt;interview is now available online&lt;/a&gt;.

&lt;blockquote&gt;
Joey McAllister speaks with Antony Marcano about his STAREAST tutorial, "Behind Every Bug is a Story," as well as some of the other conference sessions that Antony attended and enjoyed.</description>
<pubDate>Thu, 05 Jun 2008 09:19:18 -0500</pubDate></item>
<item>
 <title>QA &amp; Testing... aren't they the same?</title>
 <link>http://www.testingreflections.com/node/view/7044</link>
 <description>The short answer is "no".&lt;br /&gt;
&lt;br /&gt;
Several people have found my explanation of it useful so I'm sharing it here...&lt;br /&gt;
&lt;br /&gt;
The QA metaphor in software development has come from other, arguably, more mature industries - such as medicine, manufacturing, construction and so on. It is about all the things that we do to increase the probability of building in quality - not just detecting when we've failed to build in quality as is the case with much software testing. In this regard, testing is more analogous to quality control or, QC.&lt;br /&gt;
&lt;br /&gt;
In simple terms:&lt;br /&gt;
&lt;b&gt;QC helps us answer the question 'does our &lt;i&gt;product&lt;/i&gt; work?'&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;QA helps us answer the question 'does our &lt;i&gt;process&lt;/i&gt; work?'&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Unfortunately, many teams don't realise their process doesn't work until the testers find all the ways in which the product doesn't work... maybe that's why software testing has come to be known as QA.?</description>
<pubDate>Mon, 02 Jun 2008 08:21:15 -0500</pubDate></item>
<item>
 <title>If only software development was like listening to internet radio...</title>
 <link>http://www.testingreflections.com/node/view/6914</link>
 <description>&lt;p&gt;It's true - people who don't get TDD hear the word 'Test' and all but ignore the 'Driven Development' part of it... sometimes to the point that they assume "oh, that's that testers job then"... or the opposite happens when you hear "doesn't that mean developers spend time testing when they should be writing code?"... It can take long and hard to break through this initial cultural barrier... For a long time I've searched for a way other than dropping the word 'T' in 'TDD' to break through the inevitable barrier and I'd almost given up hope... to the point where I was about to resort to the &lt;a href="http://behaviour-driven.org/GettingTheWordsRight"&gt;BDD philosophy&lt;/a&gt;. The &lt;a href="http://www.testingreflections.com/node/view/6803"&gt;benefits of test-infection&lt;/a&gt; made me persist.&lt;/p&gt;

&lt;p&gt;To try to get people to understand the 'Driven Development' aspect of writing customer tests first a.k.a. "Acceptance Test Driven Development" (ATDD) and the relevance of the test and testing and testers and let's not forget early and frequent customer feedback... I've been using a different approach. It doesn't solve all of the problems caused by the letter 'T' but it does solve one of them - the part where people ignore the fact that the tests are &lt;i&gt;driving development&lt;/i&gt; (yes I said 'tests' not 'testers' - I emphasise this because someone recently asked me 'so, how exactly do the testers drive the developers?').&lt;/p&gt;

&lt;p&gt;So... let's talk about something else for a second... I want you to stop thinking about testing... for one moment. I want you to forget about the word 'test' and all the connotations that go along with it... I want you to think about something else... something random... let's say... 'Internet Radio'...&lt;/p&gt;</description>
<pubDate>Thu, 24 Apr 2008 12:46:28 -0500</pubDate></item>
<item>
 <title>Hackontest - 24 hour opensource programming competition</title>
 <link>http://www.testingreflections.com/node/view/6883</link>
 <description>&lt;p&gt;I'm not sure why it is called hackontest, nor am I sure why the definition of 'hacker' used on their website highlights the 'clever programmer' aspect of its origins but ignores the 'learning programming by trial and error' (i.e. not necessarily knowing about designing for maintainability and other such things)... &lt;/p&gt;

&lt;p&gt;But, they have a goal to advance one or more open source tools by having a day dedicated to adding new features to open source tools...&lt;/p&gt;

&lt;blockquote&gt;
The Swiss Open Systems User Group /ch/open organizes the first international Hackontest sponsored by Google as part of informatica08, the Swiss year of computer science 2008. Hackontest is a 24-hour programming competition of three teams of different open source projects. Its goals are to enhance popular Free Software projects according to user needs and to demonstrate to the public how enthusiastically open source software is being developed.
&lt;/blockquote&gt;

&lt;p&gt;Interested in proposing a project? Interested in voting for features? Interested in competing for the USD 8500 prize?&lt;/p&gt;

&lt;p&gt;Well - if you are, check out the &lt;a href="http://hackontest.org/index.php?action=Root-about"&gt;Hackontest website for more info...&lt;/a&gt;&lt;/p&gt;</description>
<pubDate>Sat, 19 Apr 2008 17:14:18 -0500</pubDate></item>
<item>
 <title>See you at XTC</title>
 <link>http://www.testingreflections.com/node/view/6869</link>
 <description>Tomorrow (Tuesday 15th April 2008), I'll be at &lt;a href="http://www.xpdeveloper.net/xpdwiki/Wiki.jsp?page=Xtc20080415"&gt;Extreme Tuesdays Club&lt;/a&gt; at &lt;a href="http://www.xpdeveloper.net/xpdwiki/Wiki.jsp?page=TheCountingHouse"&gt;the Counting House&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
If you want to chat about testing on Agile projects, Test Driven Development or just like beer and pie then do come along.</description>
<pubDate>Mon, 14 Apr 2008 06:04:13 -0500</pubDate></item>
</channel>
</rss>
