<?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: test cases in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/test-cases/m-p/2590395#M593030</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;Testing : During a SAP project, the core team members along with endusers test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data. &lt;/P&gt;&lt;P&gt;SAP has given atool named CATT for testing purposes.Type CATT test cases are used to test R/3 transactions automatically. The transactions usually run without user interaction. Tests are logged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type CATT test cases have two maintenance modes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CATT Create test cases. &lt;/P&gt;&lt;P&gt;Extended CATT: Create test cases with complex check logic: all CATT functions are available.&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create test cases. Use the recording functionality. You can create transaction chains that correspond with your business processes. &lt;/P&gt;&lt;P&gt;Define test rules in the test cases. &lt;/P&gt;&lt;P&gt;Create test case variants. &lt;/P&gt;&lt;P&gt;Manage the test cases in the Test Organizer. &lt;/P&gt;&lt;P&gt;Run the test cases and analyze the logs. You may have to retest test cases in which errors occurred.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;============================================================&lt;/P&gt;&lt;P&gt;Below mentioned is the example of test case for procuremnt scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INput values&lt;/P&gt;&lt;P&gt;ME21N Create PO Vendor (code) material (code) price - generates PO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ME29N Release PO (Po Number, rel code) - PO is released&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MIGO GR against PO (Mvt 101, PO number, qty, delivery note )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MIRO IR against PO ( PO number, value )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here actually against T-Code we specify what result we are expecting by inputing certain values in respective fields &amp;amp; record the output according to our business requirement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E.G.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can definitely do manual testing &amp;amp; it is not important to do it through CATT. Doing testing through CATT may save your time, but doing manual testing will again be beneficial, as you will identify the problem area easily &amp;amp; you can look forward to mend the same accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as test script is concerned, it can be designed by individual as per requirement. Eg of most probable columns are as under:&lt;/P&gt;&lt;P&gt;Customer&lt;/P&gt;&lt;P&gt;Sales area&lt;/P&gt;&lt;P&gt;Sales Order Type&lt;/P&gt;&lt;P&gt;Sales order no&lt;/P&gt;&lt;P&gt;Sales Order Date&lt;/P&gt;&lt;P&gt;Material&lt;/P&gt;&lt;P&gt;Quantity&lt;/P&gt;&lt;P&gt;Sales Order Amount&lt;/P&gt;&lt;P&gt;Sales Order Currency&lt;/P&gt;&lt;P&gt;Pricing Procedure&lt;/P&gt;&lt;P&gt;Plant&lt;/P&gt;&lt;P&gt;Shipping Point&lt;/P&gt;&lt;P&gt;Delivery Type&lt;/P&gt;&lt;P&gt;Delivery No&lt;/P&gt;&lt;P&gt;Delivery date&lt;/P&gt;&lt;P&gt;PGI no&lt;/P&gt;&lt;P&gt;PGI Accounting Document No&lt;/P&gt;&lt;P&gt;Billing Type&lt;/P&gt;&lt;P&gt;Billing No&lt;/P&gt;&lt;P&gt;Billing Amount&lt;/P&gt;&lt;P&gt;Currency&lt;/P&gt;&lt;P&gt;&amp;amp; so on........&lt;/P&gt;&lt;P&gt;Functional test case is a set of conditions or variables under which a tester will determine if a certain business process works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This test case is used for testing the system for certain business process. for example, if tester wants to test purchase order functionality so he will use functional test case which explains how to carry out the functional test. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Aug 2007 08:35:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-02T08:35:49Z</dc:date>
    <item>
      <title>test cases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/test-cases/m-p/2590394#M593029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how to write the test cases and in which transaction we need to write?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2007 08:23:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/test-cases/m-p/2590394#M593029</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-02T08:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: test cases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/test-cases/m-p/2590395#M593030</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;Testing : During a SAP project, the core team members along with endusers test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data. &lt;/P&gt;&lt;P&gt;SAP has given atool named CATT for testing purposes.Type CATT test cases are used to test R/3 transactions automatically. The transactions usually run without user interaction. Tests are logged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type CATT test cases have two maintenance modes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CATT Create test cases. &lt;/P&gt;&lt;P&gt;Extended CATT: Create test cases with complex check logic: all CATT functions are available.&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create test cases. Use the recording functionality. You can create transaction chains that correspond with your business processes. &lt;/P&gt;&lt;P&gt;Define test rules in the test cases. &lt;/P&gt;&lt;P&gt;Create test case variants. &lt;/P&gt;&lt;P&gt;Manage the test cases in the Test Organizer. &lt;/P&gt;&lt;P&gt;Run the test cases and analyze the logs. You may have to retest test cases in which errors occurred.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;============================================================&lt;/P&gt;&lt;P&gt;Below mentioned is the example of test case for procuremnt scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INput values&lt;/P&gt;&lt;P&gt;ME21N Create PO Vendor (code) material (code) price - generates PO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ME29N Release PO (Po Number, rel code) - PO is released&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MIGO GR against PO (Mvt 101, PO number, qty, delivery note )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MIRO IR against PO ( PO number, value )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here actually against T-Code we specify what result we are expecting by inputing certain values in respective fields &amp;amp; record the output according to our business requirement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E.G.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can definitely do manual testing &amp;amp; it is not important to do it through CATT. Doing testing through CATT may save your time, but doing manual testing will again be beneficial, as you will identify the problem area easily &amp;amp; you can look forward to mend the same accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as test script is concerned, it can be designed by individual as per requirement. Eg of most probable columns are as under:&lt;/P&gt;&lt;P&gt;Customer&lt;/P&gt;&lt;P&gt;Sales area&lt;/P&gt;&lt;P&gt;Sales Order Type&lt;/P&gt;&lt;P&gt;Sales order no&lt;/P&gt;&lt;P&gt;Sales Order Date&lt;/P&gt;&lt;P&gt;Material&lt;/P&gt;&lt;P&gt;Quantity&lt;/P&gt;&lt;P&gt;Sales Order Amount&lt;/P&gt;&lt;P&gt;Sales Order Currency&lt;/P&gt;&lt;P&gt;Pricing Procedure&lt;/P&gt;&lt;P&gt;Plant&lt;/P&gt;&lt;P&gt;Shipping Point&lt;/P&gt;&lt;P&gt;Delivery Type&lt;/P&gt;&lt;P&gt;Delivery No&lt;/P&gt;&lt;P&gt;Delivery date&lt;/P&gt;&lt;P&gt;PGI no&lt;/P&gt;&lt;P&gt;PGI Accounting Document No&lt;/P&gt;&lt;P&gt;Billing Type&lt;/P&gt;&lt;P&gt;Billing No&lt;/P&gt;&lt;P&gt;Billing Amount&lt;/P&gt;&lt;P&gt;Currency&lt;/P&gt;&lt;P&gt;&amp;amp; so on........&lt;/P&gt;&lt;P&gt;Functional test case is a set of conditions or variables under which a tester will determine if a certain business process works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This test case is used for testing the system for certain business process. for example, if tester wants to test purchase order functionality so he will use functional test case which explains how to carry out the functional test. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2007 08:35:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/test-cases/m-p/2590395#M593030</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-02T08:35:49Z</dc:date>
    </item>
  </channel>
</rss>

