<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ABAP UNIT - Test Driven Development in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386427#M813126</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Dirk already mentioned TDD is writing test before writing productive code. This approach is not limited to OO practices or unit tests. &lt;/P&gt;&lt;P&gt;E.g. writing an eCatt script in advance that passes as soon the scenario is working, adheres to TDD practices also..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vice versa if one practices unit testing and oo patterns it is no TDD if the tests are written after the productive code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Sep 2010 19:06:07 GMT</pubDate>
    <dc:creator>former_member183804</dc:creator>
    <dc:date>2010-09-28T19:06:07Z</dc:date>
    <item>
      <title>ABAP UNIT - Test Driven Development</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386425#M813124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear ABAPers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope some of you may have also ventured into this area of Test Driven Development.  I have just started looking into this new and exciting way of development.  My understanding after having gone through the available blogs and some reading material on TDD, is that, we have to religiously embrace Object Oriented programing to actually benefit from TDD methodology.  That raised a big question in my mind, how do we implement this technique when we are coding in the user exits like MV45AFZZ, which is mostly classical ABAP programming?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me understand the TDD a bit more than I currently do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks much,&lt;/P&gt;&lt;P&gt;SMA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&amp;lt;- removed by moderator -&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Neil Gardiner on Sep 29, 2010 10:38 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Feb 2008 04:28:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386425#M813124</guid>
      <dc:creator>shaik_a</dc:creator>
      <dc:date>2008-02-21T04:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP UNIT - Test Driven Development</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386426#M813125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;TDD means that you first write a test and in the second step the coding making the test pass. As this technique comes from the OO--world all articles are surely about OO but in ABAP-word you  can also write unit tests for FORMs or FUNCTIONS. Otherwise you can but all your logic in a global class and call this from within your user-exit. Within the global class you have all support for the unit-tests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps you&lt;/P&gt;&lt;P&gt;Dirk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Sep 2010 19:40:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386426#M813125</guid>
      <dc:creator>dirk_wittenberg</dc:creator>
      <dc:date>2010-09-26T19:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP UNIT - Test Driven Development</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386427#M813126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Dirk already mentioned TDD is writing test before writing productive code. This approach is not limited to OO practices or unit tests. &lt;/P&gt;&lt;P&gt;E.g. writing an eCatt script in advance that passes as soon the scenario is working, adheres to TDD practices also..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vice versa if one practices unit testing and oo patterns it is no TDD if the tests are written after the productive code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Sep 2010 19:06:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386427#M813126</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2010-09-28T19:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP UNIT - Test Driven Development</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386428#M813127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you looked at the code inside the methods?  Mostly looks like classic ABAP to me  &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Sep 2010 20:17:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-driven-development/m-p/3386428#M813127</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-28T20:17:23Z</dc:date>
    </item>
  </channel>
</rss>

