<?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 test coverage in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/test-coverage/m-p/82147#M33621</link>
    <description>&lt;P&gt;White building a test suite that will be used for validation or&amp;nbsp; for regression testing , it will be useful after running this test suite to have a kind of code coverage (or Process stages coverage) &amp;nbsp;information.&lt;/P&gt;
&lt;P&gt;This code coverage can provide us with statistics like:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;% of items in the process we didn't path through. (it will be a good coverage indicator)&lt;/LI&gt;
&lt;LI&gt;A list of these Items so we can enrich our test and enhance our test coverage.&lt;/LI&gt;
&lt;LI&gt;Number of times we passed in the same path or sequence, so we can optimise our test suite by reducing test without compromising quality.&lt;/LI&gt;
&lt;LI&gt;Object and objects 'actions called during these tests.&lt;/LI&gt;
&lt;LI&gt;Credentials not used, Queues not used, …&lt;/LI&gt;
&lt;LI&gt;….&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This code coverage will also help identifying in production what objects are no more used and which paths in the processes we never go through in production.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Anas Baroudi&lt;BR /&gt;ROM Architect&lt;BR /&gt;Blue Prism&lt;BR /&gt;Europe/Paris&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Thu, 20 Jun 2019 13:35:00 GMT</pubDate>
    <dc:creator>Anas</dc:creator>
    <dc:date>2019-06-20T13:35:00Z</dc:date>
    <item>
      <title>test coverage</title>
      <link>https://community.blueprism.com/t5/Product-Forum/test-coverage/m-p/82147#M33621</link>
      <description>&lt;P&gt;White building a test suite that will be used for validation or&amp;nbsp; for regression testing , it will be useful after running this test suite to have a kind of code coverage (or Process stages coverage) &amp;nbsp;information.&lt;/P&gt;
&lt;P&gt;This code coverage can provide us with statistics like:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;% of items in the process we didn't path through. (it will be a good coverage indicator)&lt;/LI&gt;
&lt;LI&gt;A list of these Items so we can enrich our test and enhance our test coverage.&lt;/LI&gt;
&lt;LI&gt;Number of times we passed in the same path or sequence, so we can optimise our test suite by reducing test without compromising quality.&lt;/LI&gt;
&lt;LI&gt;Object and objects 'actions called during these tests.&lt;/LI&gt;
&lt;LI&gt;Credentials not used, Queues not used, …&lt;/LI&gt;
&lt;LI&gt;….&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This code coverage will also help identifying in production what objects are no more used and which paths in the processes we never go through in production.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Anas Baroudi&lt;BR /&gt;ROM Architect&lt;BR /&gt;Blue Prism&lt;BR /&gt;Europe/Paris&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Jun 2019 13:35:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/test-coverage/m-p/82147#M33621</guid>
      <dc:creator>Anas</dc:creator>
      <dc:date>2019-06-20T13:35:00Z</dc:date>
    </item>
  </channel>
</rss>

