<?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 - Unit Testing</title>
 <link>http://www.oehive.org/taxonomy/term/587/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>Include Unit Code at the bottom of your class files</title>
 <link>http://www.oehive.org/node/1402</link>
 <description>&lt;p&gt;One of the important things in software development is to do unit testing - that is a set of tests the programmer can do on a piece of code to be assured it is most likely working the way one wants it to.&lt;/p&gt;
&lt;p&gt;Surprisingly it is rare to find unit test code as part of a source code file.  If it is created at all (horror), it is usually tucked away on some developers disk someplace or simply thrown away!&lt;/p&gt;
&lt;p&gt;What I have found helpful for myself as well as others working the same code, is to place a comment at the end of the program with the unit test code.&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;&lt;p&gt;&lt;a href=&quot;http://www.oehive.org/node/1402&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.oehive.org/node/1402#comments</comments>
 <category domain="http://www.oehive.org/taxonomy/term/587">Unit Testing</category>
 <category domain="http://www.oehive.org/taxonomy/term/132">Code Quality &amp;amp; Improvement</category>
 <category domain="http://www.oehive.org/taxonomy/term/133">Coding Standards and Best Practice</category>
 <category domain="http://www.oehive.org/taxonomy/term/136">OOABL</category>
 <group domain="http://www.oehive.org/ooabl">Object-Oriented ABL Techniques</group>
 <group domain="http://www.oehive.org/node/667">ABL(4GL) General Programming Group</group>
 <pubDate>Wed, 04 Feb 2009 05:32:12 +0000</pubDate>
 <dc:creator>Scott Auge</dc:creator>
 <guid isPermaLink="false">1402 at http://www.oehive.org</guid>
</item>
</channel>
</rss>
