<?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 class method call sequence determination in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259224#M778598</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anubhav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the setup() method is intended to initialize a fixture common to all test methods. To differ (rely) on the test progress so far and have a conditional logic is no good idea. These will make the code complex and thus hard to understand. Additionaly it introduces the risk that test methods depend on each other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To split different test methods according to a common fixture to a common test class as Uwe suggested is one possibilty. Alternatively do a individual initaliziation within the test methods or delegate to some ordinary service method. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy New Year&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Jan 2008 10:26:29 GMT</pubDate>
    <dc:creator>former_member183804</dc:creator>
    <dc:date>2008-01-04T10:26:29Z</dc:date>
    <item>
      <title>abap unit test class method call sequence determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259222#M778596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;    I have a class that has methods in my test class&lt;/P&gt;&lt;P&gt;    setup&lt;/P&gt;&lt;P&gt;    test_add&lt;/P&gt;&lt;P&gt;    test_delete&lt;/P&gt;&lt;P&gt;    teardown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the call sequence is &lt;/P&gt;&lt;P&gt;1. setup , test_add , teardown&lt;/P&gt;&lt;P&gt;2. setup , test_delete , teardown.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I wanna know how to find inside the setup() method which method was called last and which method will be called next&lt;/STRONG&gt;. I wanna do it to prepare diff set of data in setup() method&lt;/P&gt;&lt;P&gt;for different test methods.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest solutions and pointers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;anubhav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 10:59:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259222#M778596</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-03T10:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: abap unit test class method call sequence determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259223#M778597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anubhav&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the methods to be tested require completely &lt;STRONG&gt;different setups&lt;/STRONG&gt; then you have to create &lt;STRONG&gt;different test classes&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 11:14:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259223#M778597</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-01-03T11:14:44Z</dc:date>
    </item>
    <item>
      <title>Re: abap unit test class method call sequence determination</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259224#M778598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anubhav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the setup() method is intended to initialize a fixture common to all test methods. To differ (rely) on the test progress so far and have a conditional logic is no good idea. These will make the code complex and thus hard to understand. Additionaly it introduces the risk that test methods depend on each other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To split different test methods according to a common fixture to a common test class as Uwe suggested is one possibilty. Alternatively do a individual initaliziation within the test methods or delegate to some ordinary service method. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy New Year&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2008 10:26:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-unit-test-class-method-call-sequence-determination/m-p/3259224#M778598</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2008-01-04T10:26:29Z</dc:date>
    </item>
  </channel>
</rss>

