<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	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/"
		>
<channel>
	<title>Comments on: interface Excel { @MaybeEasiest businessGuyDoit(); }</title>
	<atom:link href="http://almaer.com/blog/interface-excel-maybeeasiest-businessguydoit/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/interface-excel-maybeeasiest-businessguydoit</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Tue, 03 Jan 2012 22:08:49 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joel Hockey</title>
		<link>http://almaer.com/blog/interface-excel-maybeeasiest-businessguydoit/comment-page-1#comment-29712</link>
		<dc:creator>Joel Hockey</dc:creator>
		<pubDate>Thu, 22 Dec 2005 02:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/interface-excel-maybeeasiest-businessguydoit#comment-29712</guid>
		<description>I have been using Excel with jython and POI recently to do testing of a data warehouse system and it has worked very well.

The tests are defined in Excel.  I then parse the excel file (using jython and POI) to produce jython test case methods (making use of the python unit-testing framework).  I can then manually tweak the test cases if required, but the vast majority are ready to execute directly from the Excel data.

Using excel rather than some XML format or other interface is much better.  Excel is defintely the fastest data entry interface that I have used and everyone feels comfortable with it.  By getting business users to define the business rules in an agreed format, I have a very good test suite built for very little effort.
</description>
		<content:encoded><![CDATA[<p>I have been using Excel with jython and POI recently to do testing of a data warehouse system and it has worked very well.</p>
<p>The tests are defined in Excel.  I then parse the excel file (using jython and POI) to produce jython test case methods (making use of the python unit-testing framework).  I can then manually tweak the test cases if required, but the vast majority are ready to execute directly from the Excel data.</p>
<p>Using excel rather than some XML format or other interface is much better.  Excel is defintely the fastest data entry interface that I have used and everyone feels comfortable with it.  By getting business users to define the business rules in an agreed format, I have a very good test suite built for very little effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

