https://community.appian.com/success/w/guide/3340/in-flight-testingen-USTelligent Community 12https://community.appian.com/success/w/guide/3340/in-flight-testingTue, 23 Apr 2024 13:22:46 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edAppian Max Teamhttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsCurrent Revision posted to Guide by Appian Max Team on 4/23/2024 1:22:46 PM<br /> <div style="margin:8px 16% 8px 8%;"> <h2 id="introduction">Introduction</h2> <p>When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process instances. However, any objects referenced by that process model, including constants, expression rules, interfaces, other processes, etc., will always run the latest version. Developers must take precautions to ensure that both existing and new processes will work after the deployment. In-flight testing is used to ensure all modified objects are compatible with legacy processes and have expected behavior for both active and new processes. In-flight testing is not needed for first-time releases of an application because no process instances exist in the production environment prior to deployment. However, in-flight testing should always be conducted in preparation for subsequent production releases.&nbsp;</p> <h2 id="environments">Environments</h2> <p>A Pre Production environment is best suited for in-flight testing. The Appian version and application version should mimic the current Production versions in order to maximize testing validity. In a three environment ecosystem, the Test environment is typically used to push code each sprint from the Development environment. Thus, the Test environment application version will most likely not match the Production environment application version after a given development sprint. While technically possible to conduct in-flight testing using a 3 environment ecosystem, it requires additional management and testing each sprint. With a stable Pre Production environment that continually matches Production regardless of sprint development, in-flight testing becomes truly valid and simpler to conduct.&nbsp;</p> <h2 id="test_execution">Test Execution</h2> <p>In-flight testing begins prior to deployment to a Pre Production environment. Kick off every process model in the Pre Production environment which is expected to have active instances during the actual Production deployment. This can be done manually or via automated testing tools like <a href="/b/appmarket/posts/fit-fam-fitnesse-for-appian-generator">FitNesse for Appian</a>. Ensure that each path within a process model is accounted for when staging active instances so that each part of a process model that changed since the last version may be tested. After the deployment is finished, complete the staged in-flight instances. Validate the results by comparing the intended process behavior to the actual behavior.</p> <h2 id="determining_value">Determining Value</h2> <p>If all pathways within each process instance cannot realistically be accounted for in testing, weigh the pros and cons of prioritizing a fixed set of in-flight instances to stage. Value may be based on the following characteristics:&nbsp;</p> <ul> <li>Expected in-flight production instance volume</li> <li>Time required to stage the instances in Pre Production</li> <li>Time required to complete the instance</li> <li>Business impact</li> <li>Degree of change</li> </ul> <h2 id="development_tips">Development Tips</h2> <ul> <li>Follow <a href="/w/article/3305/backward-compatible-design-planning-for-subsequent-deployments">Backwards Compatible Design</a> suggestions to help facilitate subsequent deployments of an application.</li> <li><a href="/w/guide/3064/how-to-create-flexible-processes">Create Flexible Processes</a> using a data-centric design and short-lived instances to make management of in-flight instances easier.&nbsp;</li> </ul> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing</div> https://community.appian.com/success/w/guide/3340/in-flight-testing/revision/5Tue, 31 Oct 2023 17:43:30 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edKim Dayhttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsRevision 5 posted to Guide by Kim Day on 10/31/2023 5:43:30 PM<br /> <div style="margin:8px 16% 8px 8%;"> <h2 id="introduction">Introduction</h2> <p>When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process instances. However, any objects referenced by that process model, including constants, expression rules, interfaces, other processes, etc., will always run the latest version. Developers must take precautions to ensure that both existing and new processes will work after the deployment. In-flight testing is used to ensure all modified objects are compatible with legacy processes and have expected behavior for both active and new processes. In-flight testing is not needed for first-time releases of an application because no process instances exist in the production environment prior to deployment. However, in-flight testing should always be conducted in preparation for subsequent production releases.&nbsp;</p> <h2 id="environments">Environments</h2> <p>A Pre Production environment is best suited for in-flight testing. The Appian version and application version should mimic the current Production versions in order to maximize testing validity. In a three environment ecosystem, the Test environment is typically used to push code each sprint from the Development environment. Thus, the Test environment application version will most likely not match the Production environment application version after a given development sprint. While technically possible to conduct in-flight testing using a 3 environment ecosystem, it requires additional management and testing each sprint. With a stable Pre Production environment that continually matches Production regardless of sprint development, in-flight testing becomes truly valid and simpler to conduct.&nbsp;</p> <h2 id="test_execution">Test Execution</h2> <p>In-flight testing begins prior to deployment to a Pre Production environment. Kick off every process model in the Pre Production environment which is expected to have active instances during the actual Production deployment. This can be done manually or via automated testing tools like <a href="/b/appmarket/posts/fit-fam-fitnesse-for-appian-generator">FitNesse for Appian</a>. Ensure that each path within a process model is accounted for when staging active instances so that each part of a process model that changed since the last version may be tested. After the deployment is finished, complete the staged in-flight instances. Validate the results by comparing the intended process behavior to the actual behavior.</p> <h2 id="determining_value">Determining Value</h2> <p>If all pathways within each process instance cannot realistically be accounted for in testing, weigh the pros and cons of prioritizing a fixed set of in-flight instances to stage. Value may be based on the following characteristics:&nbsp;</p> <ul> <li>Expected in-flight production instance volume</li> <li>Time required to stage the instances in Pre Production</li> <li>Time required to complete the instance</li> <li>Business impact</li> <li>Degree of change</li> </ul> <h2 id="development_tips">Development Tips</h2> <ul> <li>Follow <a href="/w/article/3305/backward-compatible-design-planning-for-subsequent-deployments">Backwards Compatible Design</a> suggestions to help facilitate subsequent deployments of an application.</li> <li><a href="/w/guide/3064/how-to-create-flexible-processes">Create Flexible Processes</a> using a data-centric design and short-lived instances to make management of in-flight instances easier.&nbsp;</li> </ul> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing</div> https://community.appian.com/success/w/guide/3340/in-flight-testing/revision/4Mon, 30 Oct 2023 20:48:13 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edmatt.cosenzahttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsRevision 4 posted to Guide by matt.cosenza on 10/30/2023 8:48:13 PM<br /> <div style="margin:8px 16% 8px 8%;"> <h2 id="introduction">Introduction</h2> <p>When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process instances. However, any objects referenced by that process model, including constants, expression rules, interfaces, other processes, etc., will always run the latest version. Developers must take precautions to ensure that both existing and new processes will work after the deployment. In-flight testing is used to ensure all modified objects are compatible with legacy processes and have expected behavior for both active and new processes. In-flight testing is not needed for first-time releases of an application because no process instances exist in the production environment prior to deployment. However, in-flight testing should always be conducted in preparation for subsequent production releases.&nbsp;</p> <h2 id="environments">Environments</h2> <p>A Pre Production environment is best suited for in-flight testing. The Appian version and application version should mimic the current Production versions in order to maximize testing validity. In a three environment ecosystem, the Test environment is typically used to push code each sprint from the Development environment. Thus, the Test environment application version will most likely not match the Production environment application version after a given development sprint. While technically possible to conduct in-flight testing using a 3 environment ecosystem, it requires additional management and testing each sprint. With a stable Pre Production environment that continually matches Production regardless of sprint development, in-flight testing becomes truly valid and simpler to conduct.&nbsp;</p> <h2 id="test_execution">Test Execution</h2> <p>In-flight testing begins prior to deployment to a Pre Production environment. Kick off every process model in the Pre Production environment which is expected to have active instances during the actual Production deployment. This can be done manually or via automated testing tools like <a href="/b/appmarket/posts/fit-fam-fitnesse-for-appian-generator">FitNesse for Appian</a>. Ensure that each path within a process model is accounted for when staging active instances so that each part of a process model that changed since the last version may be tested. After the deployment is finished, complete the staged in-flight instances. Validate the results by comparing the intended process behavior to the actual behavior.</p> <h2 id="determining_value">Determining Value</h2> <p>If all pathways within each process instance cannot realistically be accounted for in testing, weigh the pros and cons of prioritizing a fixed set of in-flight instances to stage. Value may be based on the following characteristics:&nbsp;</p> <ul> <li>Expected in-flight production instance volume</li> <li>Time required to stage the instances in Pre Production</li> <li>Time required to complete the instance</li> <li>Business impact</li> <li>Degree of change</li> </ul> <h2 id="development_tips">Development Tips</h2> <ul> <li>Follow <a href="/w/article/3305/backward-compatible-design-planning-for-subsequent-deployments">Backwards Compatible Design</a> suggestions to help facilitate subsequent deployments of an application.</li> <li><a href="/w/guide/3064/how-to-create-flexible-processes">Create Flexible Processes</a> using a data-centric design and short-lived instances to make management of in-flight instances easier.&nbsp;</li> </ul> </div><div style="clear:both;"></div> https://community.appian.com/success/w/guide/3340/in-flight-testing/revision/3Mon, 30 Oct 2023 20:47:34 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edmatt.cosenzahttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsRevision 3 posted to Guide by matt.cosenza on 10/30/2023 8:47:34 PM<br /> <div style="margin:8px 16% 8px 8%;"> <h2 id="introduction">Introduction</h2> <p>When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process instances. However, any objects referenced by that process model, including constants, expression rules, interfaces, other processes, etc., will always run the latest version. Developers must take precautions to ensure that both existing and new processes will work after the deployment. In-flight testing is used to ensure all modified objects are compatible with legacy processes and have expected behavior for both active and new processes. In-flight testing is not needed for first-time releases of an application because no process instances exist in the production environment prior to deployment. However, in-flight testing should always be conducted in preparation for subsequent production releases.&nbsp;</p> <h2 id="environments">Environments</h2> <p>A Pre Production environment is best suited for in-flight testing. The Appian version and application version should mimic the current Production versions in order to maximize testing validity. In a three environment ecosystem, the Test environment is typically used to push code each sprint from the Development environment. Thus, the Test environment application version will most likely not match the Production environment application version after a given development sprint. While technically possible to conduct in-flight testing using a 3 environment ecosystem, it requires additional management and testing each sprint. With a stable Pre Production environment that continually matches Production regardless of sprint development, in-flight testing becomes truly valid and simpler to conduct.&nbsp;</p> <h2 id="test_execution">Test Execution</h2> <p>In-flight testing begins prior to deployment to a Pre Production environment. Kick off every process model in the Pre Production environment which is expected to have active instances during the actual Production deployment. This can be done manually or via automated testing tools like <a href="/b/appmarket/posts/fit-fam-fitnesse-for-appian-generator">FitNesse for Appian</a>. Ensure that each path within a process model is accounted for when staging active instances so that each part of a process model that changed since the last version may be tested. After the deployment is finished, complete the staged in-flight instances. Validate the results by comparing the intended process behavior to the actual behavior.</p> <h2 id="determining_value">Determining Value</h2> <p>If all pathways within each process instance cannot realistically be accounted for in testing, weigh the pros and cons of prioritizing a fixed set of in-flight instances to stage. Value may be based on the following characteristics:&nbsp;</p> <ul> <li>Expected in-flight production instance volume</li> <li>Time required to stage the instances in Pre Production</li> <li>Time required to complete the instance</li> <li>Business impact</li> <li>Degree of change</li> </ul> <h2 id="">Development Tips</h2> <ul> <li>Follow <a href="/w/article/3305/backward-compatible-design-planning-for-subsequent-deployments">Backwards Compatible Design</a> suggestions to help facilitate subsequent deployments of an application.</li> <li><b><a href="/w/guide/3064/how-to-create-flexible-processes">Create Flexible Processes</a> using a data-centric design and short-lived instances to make management of in-flight instances easier.&nbsp;</b></li> </ul> </div><div style="clear:both;"></div> https://community.appian.com/success/w/guide/3340/in-flight-testing/revision/2Mon, 30 Oct 2023 20:44:44 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edmatt.cosenzahttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsRevision 2 posted to Guide by matt.cosenza on 10/30/2023 8:44:44 PM<br /> <div style="margin:8px 16% 8px 8%;"> <p><b>Introduction</b></p> <p>When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process instances. However, any objects referenced by that process model, including constants, expression rules, interfaces, other processes, etc., will always run the latest version. Developers must take precautions to ensure that both existing and new processes will work after the deployment. In-flight testing is used to ensure all modified objects are compatible with legacy processes and have expected behavior for both active and new processes. In-flight testing is not needed for first-time releases of an application because no process instances exist in the production environment prior to deployment. However, in-flight testing should always be conducted in preparation for subsequent production releases.&nbsp;</p> <p><b>Environments</b></p> <p>A Pre Production environment is best suited for in-flight testing. The Appian version and application version should mimic the current Production versions in order to maximize testing validity. In a three environment ecosystem, the Test environment is typically used to push code each sprint from the Development environment. Thus, the Test environment application version will most likely not match the Production environment application version after a given development sprint. While technically possible to conduct in-flight testing using a 3 environment ecosystem, it requires additional management and testing each sprint. With a stable Pre Production environment that continually matches Production regardless of sprint development, in-flight testing becomes truly valid and simpler to conduct.&nbsp;</p> <p><b>Executing In-Flight Testing</b></p> <p>In-flight testing begins prior to deployment to a Pre Production environment. Kick off every process model in the Pre Production environment which is expected to have active instances during the actual Production deployment. This can be done manually or via automated testing tools like <a href="/b/appmarket/posts/fit-fam-fitnesse-for-appian-generator">FitNesse for Appian</a>. Ensure that each path within a process model is accounted for when staging active instances so that each part of a process model that changed since the last version may be tested. After the deployment is finished, complete the staged in-flight instances. Validate the results by comparing the intended process behavior to the actual behavior.</p> <p><b>Determining Value</b></p> <p>If all pathways within each process instance cannot realistically be accounted for in testing, weigh the pros and cons of prioritizing a fixed set of in-flight instances to stage. Value may be based on the following characteristics:&nbsp;</p> <ul> <li>Expected in-flight production instance volume</li> <li>Time required to stage the instances in Pre Production</li> <li>Time required to complete the instance</li> <li>Business impact</li> <li>Degree of change</li> </ul> <p><b>Development Tips</b></p> <ul> <li>Follow <a href="/w/article/3305/backward-compatible-design-planning-for-subsequent-deployments">Backwards Compatible Design</a> suggestions to help facilitate subsequent deployments of an application.</li> <li><b><a href="/w/guide/3064/how-to-create-flexible-processes">Create Flexible Processes</a> using a data-centric design and short-lived instances to make management of in-flight instances easier.&nbsp;</b></li> </ul> </div><div style="clear:both;"></div> https://community.appian.com/success/w/guide/3340/in-flight-testing/revision/1Wed, 13 Sep 2023 14:05:18 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:01bc4819-226b-4c30-a50a-78ca882df5edjoel.larinhttps://community.appian.com/success/w/guide/3340/in-flight-testing#commentsRevision 1 posted to Guide by joel.larin on 9/13/2023 2:05:18 PM<br /> <p>fdasd</p><div style="clear:both;"></div>