<?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: Unit Testing concept in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141994#M1191812</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Parameter QUIT of the ASSERT_EQUALS will determine what to do after you got assertion in the CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this below example, test execution will contine even if assertion would be raised by the first call because we have specified CL_AUNIT_ASSERT=&amp;gt;NO. But it will terminate the method if the second call fails because we haven't specified any this thing.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
METHOD TEST_1.
...
CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab1&amp;gt;
         EXP = &amp;lt;e_tab1&amp;gt;
         QUIT = CL_AUNIT_ASSERT=&amp;gt;NO  " &amp;lt;&amp;lt;
         MSG = 'Main data not matching').

CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab2&amp;gt;
         EXP = &amp;lt;e_tab2&amp;gt;
         MSG = 'Main data not matching').

CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab3&amp;gt;
         EXP = &amp;lt;e_tab3&amp;gt;
         QUIT = CL_AUNIT_ASSERT=&amp;gt;NO
         MSG = 'Main data not matching').

ENDMETHOD.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, you should set the value of the parameter QUIT if you want to stop:&lt;/P&gt;&lt;P&gt;Current test Method use CL_AUNIT_ASSERT=&amp;gt;METHOD&lt;/P&gt;&lt;P&gt;Current test Class use CL_AUNIT_ASSERT=&amp;gt;CLASS&lt;/P&gt;&lt;P&gt;Current program use CL_AUNIT_ASSERT=&amp;gt;PROGRAM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Jan 2009 22:41:10 GMT</pubDate>
    <dc:creator>naimesh_patel</dc:creator>
    <dc:date>2009-01-21T22:41:10Z</dc:date>
    <item>
      <title>Unit Testing concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141993#M1191811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to test some 10 scenario,In  Every scenario 1 table is  expect and 1 get  for actual .&lt;/P&gt;&lt;P&gt;For that  i want to use for every scenario the class below,&lt;/P&gt;&lt;P&gt;Something that i miss what happen if there is problem in &lt;STRONG&gt;table1&lt;/STRONG&gt; and in  &lt;STRONG&gt;table2&lt;/STRONG&gt; the program continue and display the both problems or it exit and bring just the problem in table1.&lt;/P&gt;&lt;P&gt;if so there is a way to bring all the tables errors?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;cl_aunit_assert=&amp;gt;assert_equals( exp = &amp;lt;table1&amp;gt; quit = cl_aunit_assert=&amp;gt;no act = table1  msg = msg ).
cl_aunit_assert=&amp;gt;assert_equals( exp = &amp;lt;table2&amp;gt; quit = cl_aunit_assert=&amp;gt;no act = table2  msg = msg ).&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;And so on....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2009 21:02:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141993#M1191811</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-21T21:02:13Z</dc:date>
    </item>
    <item>
      <title>Re: Unit Testing concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141994#M1191812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Parameter QUIT of the ASSERT_EQUALS will determine what to do after you got assertion in the CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this below example, test execution will contine even if assertion would be raised by the first call because we have specified CL_AUNIT_ASSERT=&amp;gt;NO. But it will terminate the method if the second call fails because we haven't specified any this thing.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
METHOD TEST_1.
...
CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab1&amp;gt;
         EXP = &amp;lt;e_tab1&amp;gt;
         QUIT = CL_AUNIT_ASSERT=&amp;gt;NO  " &amp;lt;&amp;lt;
         MSG = 'Main data not matching').

CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab2&amp;gt;
         EXP = &amp;lt;e_tab2&amp;gt;
         MSG = 'Main data not matching').

CL_AUNIT_ASSERT=&amp;gt;ASSERT_EQUALS(
         ACT = &amp;lt;a_tab3&amp;gt;
         EXP = &amp;lt;e_tab3&amp;gt;
         QUIT = CL_AUNIT_ASSERT=&amp;gt;NO
         MSG = 'Main data not matching').

ENDMETHOD.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, you should set the value of the parameter QUIT if you want to stop:&lt;/P&gt;&lt;P&gt;Current test Method use CL_AUNIT_ASSERT=&amp;gt;METHOD&lt;/P&gt;&lt;P&gt;Current test Class use CL_AUNIT_ASSERT=&amp;gt;CLASS&lt;/P&gt;&lt;P&gt;Current program use CL_AUNIT_ASSERT=&amp;gt;PROGRAM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Jan 2009 22:41:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141994#M1191812</guid>
      <dc:creator>naimesh_patel</dc:creator>
      <dc:date>2009-01-21T22:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unit Testing concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141995#M1191813</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naimesh ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can elaborate on this please,&lt;/P&gt;&lt;P&gt;I don't sure if i understand it ,example will help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Current test Method use CL_AUNIT_ASSERT=&amp;gt;METHOD
Current test Class use CL_AUNIT_ASSERT=&amp;gt;CLASS
Current program use CL_AUNIT_ASSERT=&amp;gt;PROGRAM&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2009 08:32:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141995#M1191813</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-22T08:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Unit Testing concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141996#M1191814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These values for the parameter QUIT will determine the execution of the next test method, test class or entire program in case of the failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you use QUIT = CL_AUNIT_ASSERT=&amp;gt;METHOD, ABAP Unit farmework will not execute any test method in the same test class if this assertion fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you use QUIT = CL_AUNIT_ASSERT=&amp;gt;CLASS, ABAP Unit farmework will exit from current test class if this assertion fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest to go through this TechEd session:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/395c5770-0701-0010-039b-f3ef11ac555e" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/395c5770-0701-0010-039b-f3ef11ac555e&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look for the section "Test Sequence of Failed Tests"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jan 2009 14:19:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unit-testing-concept/m-p/5141996#M1191814</guid>
      <dc:creator>naimesh_patel</dc:creator>
      <dc:date>2009-01-22T14:19:52Z</dc:date>
    </item>
  </channel>
</rss>

