<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Maverick Tester - software tester</title>
	
	<link>http://mavericktester.com</link>
	<description>The startup's software tester</description>
	<lastBuildDate>Sat, 06 Feb 2010 01:05:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForTestingTimes" /><feedburner:info uri="commentsfortestingtimes" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Comment on Back To Basics: Automated Testing by Peter</title>
		<link>http://feedproxy.google.com/~r/CommentsForTestingTimes/~3/gmKnsUi7Coo/back-to-basics-automated-testing</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 06 Feb 2010 01:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://mavericktester.com/?p=555#comment-1049</guid>
		<description>hi,

I would suggest that there is an advantage in thinking of automation as applying to tasks rather than testing.  This then leads to the question "what tasks do I do that could be better served by automation"  From this we can then ask  "what is the appropriate tool/s to automate the tasks?  We can then really get some traction.  I encourage testers to think about what they do in this context and they have built and use lots of tools to make tasks easier.  Imagine a tool whereby you can enter information about the validation of a UI or a data file (including business rules) and the tool determines the equivalence classes and boundary conditions best suited to test that element and lists them in a test condition/test case matrix that you can then use to either create files or parameters for a test tool.  You can then either create and submit  files automatically from the matrix or use the matrix as parameters for automation.  You can extend this further to the point that starting with the creation of the test matrix you can go from creation through execution and validation to flagging defects, creating a report and sending it to your boss!  All this is has been done starting with the premis "what tasks do I do that could be better served by automation"</description>
		<content:encoded><![CDATA[<p>hi,</p>
<p>I would suggest that there is an advantage in thinking of automation as applying to tasks rather than testing.  This then leads to the question &#8220;what tasks do I do that could be better served by automation&#8221;  From this we can then ask  &#8220;what is the appropriate tool/s to automate the tasks?  We can then really get some traction.  I encourage testers to think about what they do in this context and they have built and use lots of tools to make tasks easier.  Imagine a tool whereby you can enter information about the validation of a UI or a data file (including business rules) and the tool determines the equivalence classes and boundary conditions best suited to test that element and lists them in a test condition/test case matrix that you can then use to either create files or parameters for a test tool.  You can then either create and submit  files automatically from the matrix or use the matrix as parameters for automation.  You can extend this further to the point that starting with the creation of the test matrix you can go from creation through execution and validation to flagging defects, creating a report and sending it to your boss!  All this is has been done starting with the premis &#8220;what tasks do I do that could be better served by automation&#8221;</p>
<img src="http://feeds.feedburner.com/~r/CommentsForTestingTimes/~4/gmKnsUi7Coo" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://mavericktester.com/back-to-basics-automated-testing#comment-1049</feedburner:origLink></item>
	<item>
		<title>Comment on It’s time to grow up and ditch the security blanket by Anne-Marie Charrett</title>
		<link>http://feedproxy.google.com/~r/CommentsForTestingTimes/~3/d2UteLWcNcc/its-time-to-grow-up-and-ditch-the-security-blanket</link>
		<dc:creator>Anne-Marie Charrett</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://mavericktester.com/?p=575#comment-1048</guid>
		<description>Brilliantly put and so much better when expressed in &gt; 140 characters! 

I like you thoughts on test management. Most test managers I know are quite ambitious, which is why they ended up as TM's, because they wanted to challenge themselves more. Its a pity that the only outlet they feel open to them is through ensuring a process is well implemented.</description>
		<content:encoded><![CDATA[<p>Brilliantly put and so much better when expressed in &gt; 140 characters! </p>
<p>I like you thoughts on test management. Most test managers I know are quite ambitious, which is why they ended up as TM&#8217;s, because they wanted to challenge themselves more. Its a pity that the only outlet they feel open to them is through ensuring a process is well implemented.</p>
<img src="http://feeds.feedburner.com/~r/CommentsForTestingTimes/~4/d2UteLWcNcc" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://mavericktester.com/its-time-to-grow-up-and-ditch-the-security-blanket#comment-1048</feedburner:origLink></item>
	<item>
		<title>Comment on It’s time to grow up and ditch the security blanket by James Christie</title>
		<link>http://feedproxy.google.com/~r/CommentsForTestingTimes/~3/_rLd0TJqAwc/its-time-to-grow-up-and-ditch-the-security-blanket</link>
		<dc:creator>James Christie</dc:creator>
		<pubDate>Fri, 05 Feb 2010 14:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://mavericktester.com/?p=575#comment-1047</guid>
		<description>"A life worth living will take you out of your comfort zone time and time again"

Indeed. The only way to grow is to scare yourself now and again.

This is related to the discussion we were having yesterday on Twitter. There's a temptation for test managers to take refuge in the security of the "process". The world might be changing, and the technology may be unrecognisable from when we were young, but understanding and following a well-established process gives us a transferrable skill.

Well, yes, up to a point, but that point is very limited. If you rely on it to keep yourself employed you're basically painting yourself into a corner from which there will ultimately be no escape.

We need to accept that in a changing world, we need to change too. That's scary, but it's good. Testing would be deadly dull if nothing changed. 

We need to be clear headed enough to face up to the need to leave our comfort zone, change and adapt, but we also need the confidence to believe that we'll cope. Why shouldn't we believe that? The alternative is to believe that everyone else is better and more adaptable than us.

Everyone is ultimately facing the same challenges. The differences between us are the extent to which we're prepared to face up to that.</description>
		<content:encoded><![CDATA[<p>&#8220;A life worth living will take you out of your comfort zone time and time again&#8221;</p>
<p>Indeed. The only way to grow is to scare yourself now and again.</p>
<p>This is related to the discussion we were having yesterday on Twitter. There&#8217;s a temptation for test managers to take refuge in the security of the &#8220;process&#8221;. The world might be changing, and the technology may be unrecognisable from when we were young, but understanding and following a well-established process gives us a transferrable skill.</p>
<p>Well, yes, up to a point, but that point is very limited. If you rely on it to keep yourself employed you&#8217;re basically painting yourself into a corner from which there will ultimately be no escape.</p>
<p>We need to accept that in a changing world, we need to change too. That&#8217;s scary, but it&#8217;s good. Testing would be deadly dull if nothing changed. </p>
<p>We need to be clear headed enough to face up to the need to leave our comfort zone, change and adapt, but we also need the confidence to believe that we&#8217;ll cope. Why shouldn&#8217;t we believe that? The alternative is to believe that everyone else is better and more adaptable than us.</p>
<p>Everyone is ultimately facing the same challenges. The differences between us are the extent to which we&#8217;re prepared to face up to that.</p>
<img src="http://feeds.feedburner.com/~r/CommentsForTestingTimes/~4/_rLd0TJqAwc" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://mavericktester.com/its-time-to-grow-up-and-ditch-the-security-blanket#comment-1047</feedburner:origLink></item>
</channel>
</rss>
