<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: What are best practices for testing processes in ERP environment (Thread)</title><description> &#xD;
&#xD;
&#xD;
We have started using SpiraTest as test tool for our ERP upgrade activities. As part of the testing we also execute Integration test where we track a specific transaction through the different stages (e.g. submit purchase orde fro supplier, register material receipt for this Purchase Order, enter payables invoice, match invoice to the receipt, pay invoice).  One way to put this in SpiraTest is to define a Test Set, where the Test Set represents the complete process. Then we assign individual Test Cases to this Test Set, where each test cases represents a specific process step (e.g. Create Purchase Order), and optionally weassign these test cases to different individuals/roles so the process can flow from Procurement to Materials to Finance.  Are there may be other ways for configuring these process tests that somebody came accross in their test environment?     </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/best-practices/1366.aspx</link><item><guid isPermaLink="false">threadId=1366</guid><author>Marcel Verharen (marcel.verharen@meritor.com)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">erp testing</category><title>What are best practices for testing processes in ERP environment</title><description> &#xD;
&#xD;
&#xD;
We have started using SpiraTest as test tool for our ERP upgrade activities. As part of the testing we also execute Integration test where we track a specific transaction through the different stages (e.g. submit purchase orde fro supplier, register material receipt for this Purchase Order, enter payables invoice, match invoice to the receipt, pay invoice).  One way to put this in SpiraTest is to define a Test Set, where the Test Set represents the complete process. Then we assign individual Test Cases to this Test Set, where each test cases represents a specific process step (e.g. Create Purchase Order), and optionally weassign these test cases to different individuals/roles so the process can flow from Procurement to Materials to Finance.  Are there may be other ways for configuring these process tests that somebody came accross in their test environment?     </description><pubDate>Tue, 16 Feb 2016 13:42:01 -0500</pubDate><a10:updated>2022-10-03T17:40:51-04:00</a10:updated><link>/Support/Forum/spiratest/best-practices/1366.aspx</link></item><item><guid isPermaLink="false">messageId=2499</guid><author>Inflectra Sarah (donotreply6@kronodesk.net)</author><title>&#xD;
Hi Marcel&#xD;
&#xD;
    The design of the Test Sets module was influenced by the need to do ERP testing. </title><description>&#xD;
Hi Marcel&#xD;
&#xD;
    The design of the Test Sets module was influenced by the need to do ERP testing. Many years ago a customer in the USA was testing an ERP upgrade and needed a way to have a single data record (a purchase request &gt; purchase order, etc.) move through a scenario with different testers performing roles (person A creates the PR, person B approves the PR and it becomes a PO, person C receives the invoice, etc.).     To address this need we added a Owner field to the individual test cases in the test set to allow for this possibility.     Regards Sarah </description><pubDate>Tue, 23 Feb 2016 18:09:25 -0500</pubDate><a10:updated>2016-02-23T18:09:25-05:00</a10:updated><link>/Support/Forum/spiratest/best-practices/1366.aspx#reply2499</link></item></channel></rss>