<?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: abt unit  test plan in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317604#M794682</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi bramara,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unit testing is used to test the proper working of a single module.&lt;/P&gt;&lt;P&gt;Integration testing is used to test the integration between the modules,&lt;/P&gt;&lt;P&gt;when the complete business scenario of a client is tested (say from sales order creation to receipt of money from customer). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unit Testing&lt;/P&gt;&lt;P&gt;When you test every single document is called unit testing.&lt;/P&gt;&lt;P&gt;String Testing&lt;/P&gt;&lt;P&gt;One transaction full activity is called string testing. For example Vendor&lt;/P&gt;&lt;P&gt;invoice, goods received and vendor payment.&lt;/P&gt;&lt;P&gt;Integration Testing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is purely with other modules and we have to check whether the FI testing&lt;/P&gt;&lt;P&gt;is working with other related modules or not.&lt;/P&gt;&lt;P&gt;Testing of combined parts of an application to determine if they function&lt;/P&gt;&lt;P&gt;together correctly.There are three types of integration testing.1. Big bang&lt;/P&gt;&lt;P&gt;testing: Testing with all modules combined together invariable of its&lt;/P&gt;&lt;P&gt;levels. Often done for small projects.2. Bottom up test:Testing by&lt;/P&gt;&lt;P&gt;integrating lower level modules and ascending towards the higher-level&lt;/P&gt;&lt;P&gt;modules.3. Top down: Testing the higher-level modules and descending towards&lt;/P&gt;&lt;P&gt;the lower level modules.This can be accomplished with dummy modules to&lt;/P&gt;&lt;P&gt;replace the under construction modules with so-called stubs and drivers.&lt;/P&gt;&lt;P&gt;not.&lt;/P&gt;&lt;P&gt;Regression Testing&lt;/P&gt;&lt;P&gt;Testing for whole database. Bring all the data into another server and do&lt;/P&gt;&lt;P&gt;the testing is called regression.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;kushagra&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Jan 31, 2008 9:45 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Jan 2008 14:37:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-31T14:37:00Z</dc:date>
    <item>
      <title>abt unit  test plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317601#M794679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;can u plz explain abt unit test planning?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;es&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 13:40:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317601#M794679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-31T13:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: abt unit  test plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317602#M794680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Brahmara&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unit Testing &lt;/P&gt;&lt;P&gt;   1. A process for verifying that software, a system, or a system component performs its intended functions.&lt;/P&gt;&lt;P&gt;   2. Unit transactions are tested against their own specifications and design documents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you need to come with all sorts of scenarios, which are possible in production and test ur code if it sustains all such conditions.. so you need to make a plan of all scenarios.. before object is moved to Quality server..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Jan 31, 2008 9:19 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 14:10:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317602#M794680</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2008-01-31T14:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: abt unit  test plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317603#M794681</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;In simple term test results of the program like (input, output) with different scenario's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sriram Ponna.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 14:34:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317603#M794681</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-31T14:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: abt unit  test plan</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317604#M794682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi bramara,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unit testing is used to test the proper working of a single module.&lt;/P&gt;&lt;P&gt;Integration testing is used to test the integration between the modules,&lt;/P&gt;&lt;P&gt;when the complete business scenario of a client is tested (say from sales order creation to receipt of money from customer). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unit Testing&lt;/P&gt;&lt;P&gt;When you test every single document is called unit testing.&lt;/P&gt;&lt;P&gt;String Testing&lt;/P&gt;&lt;P&gt;One transaction full activity is called string testing. For example Vendor&lt;/P&gt;&lt;P&gt;invoice, goods received and vendor payment.&lt;/P&gt;&lt;P&gt;Integration Testing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is purely with other modules and we have to check whether the FI testing&lt;/P&gt;&lt;P&gt;is working with other related modules or not.&lt;/P&gt;&lt;P&gt;Testing of combined parts of an application to determine if they function&lt;/P&gt;&lt;P&gt;together correctly.There are three types of integration testing.1. Big bang&lt;/P&gt;&lt;P&gt;testing: Testing with all modules combined together invariable of its&lt;/P&gt;&lt;P&gt;levels. Often done for small projects.2. Bottom up test:Testing by&lt;/P&gt;&lt;P&gt;integrating lower level modules and ascending towards the higher-level&lt;/P&gt;&lt;P&gt;modules.3. Top down: Testing the higher-level modules and descending towards&lt;/P&gt;&lt;P&gt;the lower level modules.This can be accomplished with dummy modules to&lt;/P&gt;&lt;P&gt;replace the under construction modules with so-called stubs and drivers.&lt;/P&gt;&lt;P&gt;not.&lt;/P&gt;&lt;P&gt;Regression Testing&lt;/P&gt;&lt;P&gt;Testing for whole database. Bring all the data into another server and do&lt;/P&gt;&lt;P&gt;the testing is called regression.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;kushagra&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Jan 31, 2008 9:45 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 14:37:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abt-unit-test-plan/m-p/3317604#M794682</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-31T14:37:00Z</dc:date>
    </item>
  </channel>
</rss>

