<?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: Coverage Analyzer for Unit Test? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/coverage-analyzer-for-unit-test/m-p/4861009#M1136622</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rüdiger,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are right the combination of SCOV and ABAP Unit is quite natural. And yes in most of the available releases they to hardly team up. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With releases &amp;gt; 7.01 (SAP Netweaver) there will be dedicated support for the scenario you have described. For all releases &amp;lt;= 7.01 it is virtually impossible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Feb 2009 16:29:59 GMT</pubDate>
    <dc:creator>former_member183804</dc:creator>
    <dc:date>2009-02-17T16:29:59Z</dc:date>
    <item>
      <title>Coverage Analyzer for Unit Test?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/coverage-analyzer-for-unit-test/m-p/4861008#M1136621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think it would be a good idea to check the coverage of unit tests: If I run "module test" - are all the methods of the object under test processed by the unit tests?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A simple procedure should be available for this. Like an ST05 trace, the procedure could be like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Switch on the coverage analyzer&lt;/P&gt;&lt;P&gt;- Run the module tests for a single code unit&lt;/P&gt;&lt;P&gt;- Switch off the coverage analyzer and view the results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have no experience with transaction SCOV. Would it be that simple to use it for isolated, simple unit test coverage? As far as I have looked at it, it seems a much more heavy-weight transaction which is not so easy to use for such a simple purposes. Is this right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did anybody make steps in this direction so far?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rüdiger&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2008 07:57:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/coverage-analyzer-for-unit-test/m-p/4861008#M1136621</guid>
      <dc:creator>Ruediger_Plantiko</dc:creator>
      <dc:date>2008-11-25T07:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: Coverage Analyzer for Unit Test?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/coverage-analyzer-for-unit-test/m-p/4861009#M1136622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rüdiger,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are right the combination of SCOV and ABAP Unit is quite natural. And yes in most of the available releases they to hardly team up. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With releases &amp;gt; 7.01 (SAP Netweaver) there will be dedicated support for the scenario you have described. For all releases &amp;lt;= 7.01 it is virtually impossible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Feb 2009 16:29:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/coverage-analyzer-for-unit-test/m-p/4861009#M1136622</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2009-02-17T16:29:59Z</dc:date>
    </item>
  </channel>
</rss>

