<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.oehive.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The OpenEdge Hive - testing</title>
 <link>http://www.oehive.org/taxonomy/term/302/0</link>
 <description></description>
 <language>oehive</language>
<item>
 <title>Employing AppServer Made Easy</title>
 <link>http://www.oehive.org/node/1911</link>
 <description>&lt;p&gt;Many companies are contemplating to use AppServer, but are deadly afraid of doing so. Here are some thoughts about how to make developing and maintaining AppServer applications easy and very feasible.&lt;/p&gt;
&lt;p&gt;There are three main issues I encountered over the years:&lt;/p&gt;
&lt;h3&gt;a) Increased Development Time:&lt;/h3&gt;
&lt;p&gt;I used to think, that the top-main issue that AppServer novices run into is the amount of time it takes to get a program working, if the back-end is on the AppServer, which the front-end is using to access data.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/OERAGroup&quot; class=&quot;og_links&quot;&gt;OERA Group&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.oehive.org/node/1911&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/node/1911#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/256">appserver</category>
 <category domain="http://www.oehive.org/taxonomy/term/913">general ABL</category>
 <category domain="http://www.oehive.org/taxonomy/term/910">programming style</category>
 <category domain="http://www.oehive.org/taxonomy/term/911">spaghetti</category>
 <category domain="http://www.oehive.org/taxonomy/term/912">structured programming</category>
 <category domain="http://www.oehive.org/taxonomy/term/302">testing</category>
 <category domain="http://www.oehive.org/taxonomy/term/587">Unit Testing</category>
 <group domain="http://www.oehive.org/node/667">ABL(4GL) General Programming Group</group>
 <group domain="http://www.oehive.org/OERAGroup">OERA Group</group>
 <pubDate>Tue, 22 Feb 2011 17:33:57 +0000</pubDate>
 <dc:creator>hutegger</dc:creator>
 <guid isPermaLink="false">1911 at http://www.oehive.org</guid>
</item>
<item>
 <title>OEUnit - Unit Testing Framework</title>
 <link>http://www.oehive.org/project/OEUnit</link>
 <description>&lt;p&gt;=============================================================================&lt;/p&gt;
&lt;h2&gt;Update: &lt;br&gt;Project moved to &lt;a href=&quot;https://github.com/CameronWills/OEUnit&quot;&gt;GitHub&lt;/a&gt;. Feel free to fork and make changes, and I will endeavour to integrate any pull requests.&lt;/h2&gt;
&lt;p&gt;&lt;br&gt;&lt;br /&gt;
&lt;span class=&quot;inline center&quot; style=&quot;width: 734px;&quot;&gt;&lt;img src=&quot;http://www.oehive.org/files/images/OEUnit_Simple1.png&quot; alt=&quot;Screenshot: OEUnit results from running a simple test case.&quot; title=&quot;Screenshot: OEUnit results from running a simple test case.&quot;  class=&quot;image _original&quot; width=&quot;734&quot; height=&quot;536&quot; /&gt;&lt;span class=&quot;caption&quot; style=&quot;width: 732px;&quot;&gt;&lt;strong&gt;Screenshot: OEUnit results from running a simple test case.&lt;/strong&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/node/667&quot; class=&quot;og_links&quot;&gt;ABL(4GL) General Programming Group&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description>
 <category domain="http://www.oehive.org/taxonomy/term/565">framework</category>
 <category domain="http://www.oehive.org/taxonomy/term/566">oeunit</category>
 <category domain="http://www.oehive.org/taxonomy/term/563">test</category>
 <category domain="http://www.oehive.org/taxonomy/term/302">testing</category>
 <category domain="http://www.oehive.org/taxonomy/term/564">unit</category>
 <category domain="http://www.oehive.org/taxonomy/term/567">Testing Tools</category>
 <group domain="http://www.oehive.org/ooabl">Object-Oriented ABL Techniques</group>
 <group domain="http://www.oehive.org/devtools">Development Tools Group</group>
 <group domain="http://www.oehive.org/node/667">ABL(4GL) General Programming Group</group>
 <pubDate>Sat, 01 Nov 2008 00:08:38 +0000</pubDate>
 <dc:creator>cwills</dc:creator>
 <guid isPermaLink="false">1361 at http://www.oehive.org</guid>
</item>
<item>
 <title>ProUnit - unit testing framework</title>
 <link>http://www.oehive.org/node/730</link>
 <description>&lt;p&gt;ProUnit is a framework to create automated unit tests for Progress 4GL platform. It&#039;s based on other XUnit frameworks, like JUnit, NUnit and others.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li  class=&quot;first last og_links&quot;&gt;&lt;a href=&quot;/node/667&quot; class=&quot;og_links&quot;&gt;ABL(4GL) General Programming Group&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description>
 <comments>http://www.oehive.org/node/730#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/302">testing</category>
 <category domain="http://www.oehive.org/taxonomy/term/567">Testing Tools</category>
 <group domain="http://www.oehive.org/devtools">Development Tools Group</group>
 <group domain="http://www.oehive.org/node/667">ABL(4GL) General Programming Group</group>
 <pubDate>Thu, 22 Feb 2007 00:09:51 +0000</pubDate>
 <dc:creator>jurjen</dc:creator>
 <guid isPermaLink="false">730 at http://www.oehive.org</guid>
</item>
<item>
 <title>Prolint</title>
 <link>http://www.oehive.org/prolint</link>
 <description>&lt;p&gt;Prolint is a tool for automated source code review of Progress 4GL code. It reads one or more sourcefiles and examines it for bad programming practice&lt;/p&gt;
&lt;p&gt;When you are interested Prolint, you are encouraged to subscribe to this group where you find the on-line tools to collaborate and discuss Prolint. There is a discussion forum, you can submit issues (for bugs and enhancement requests), you can modify the on-line documentation. So subscribe, and then don&#039;t forget to go to your subscription details to enable the e-mail notification!&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <category domain="http://www.oehive.org/taxonomy/term/154">developer tools</category>
 <category domain="http://www.oehive.org/taxonomy/term/222">Progress development tool</category>
 <category domain="http://www.oehive.org/taxonomy/term/155">Prolint</category>
 <category domain="http://www.oehive.org/taxonomy/term/302">testing</category>
 <category domain="http://www.oehive.org/taxonomy/term/131">Code Parsing</category>
 <category domain="http://www.oehive.org/taxonomy/term/132">Code Quality &amp;amp; Improvement</category>
 <category domain="http://www.oehive.org/taxonomy/term/214">Development Support Tools</category>
 <category domain="http://www.oehive.org/taxonomy/term/150">All Projects</category>
 <pubDate>Sat, 16 Sep 2006 12:28:20 +0000</pubDate>
 <dc:creator>jurjen</dc:creator>
 <guid isPermaLink="false">223 at http://www.oehive.org</guid>
</item>
</channel>
</rss>
