--- title: "Forced Interactions" canonical: "https://docs.getxray.app/space/XRAY/160235553/Forced%20Interactions" format: markdown --- ![Banner-Xray-Documentation-Enterprise.png](media://34ee3ef2-dd9f-48d8-8bd0-dd7e6a9503b8) > Macro (ui-expand) > > > Macro (toc) # Introduction This section explains how to use the Forced Interactions feature of [Xray Test Case Designer](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160038931). Forced Interactions are a method to train the model about specific business rules that must always be considered on the generated Tests, as long as the required values and outcomes. With Forced Interactions, the system will always make sure these interactions are added to your model output. Forced Interactions enhance the precision, coverage, and control over Test [Scenarios](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160137241), making the testing process more robust and efficient. # Operations ## When to Use Forced Interactions If you need Xray Test Case Designer Tests to include a particular Test for a required business rule, for example: > **Requirement: (#2947 – Notify about Certain High Risk Flood Zone Applications)** > > The business rule that you want to test reads, “if a regular applicant applies for a large loan in a flood zone with 90% LTV, send the notification to the manager.” In our example, you must have these specific four values included together in a single Test: - The customer status must be *Regular*. - Loan to value ratio must be 90%. - Loan amount must be *Large*. - The property needs to be In a Flood Zone. > ℹ️ Go to the Forced Interactions screen under *Rules* (Figure 3) and add your Scenario. ## Using Forced Interactions > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > ℹ️ - This feature is not just for “official requirements.” Consider including other critical elements in your Xray Test Case Designer-generated suite, such as a forced scenario that contains the most common value for each Parameter (i.e., the *Happy Path*). > > ℹ️ - As noted above, you don’t need to specify every value. In fact, it’s better to only force the values needed to trigger the Requirement or business rule. This allows for the greatest variation in your Xray Test Case Designer-generated Tests. > > ℹ️ - Keep the concept of *Expected Results* clearly separated from ordinary parameters and values in your mind. Treat them differently when entering your test models. Typically, you should not enter Expected Result values in the Parameters screen. [The primary places to enter Expected Results are the Forced Interactions and Scripts screens](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301702562). > > ℹ️ - Use this feature selectively. Remember, many combinations will automatically appear in your Xray Test Case Designer-generated models without requiring any special action. For example, if a business rule only requires two values to appear together, that requirement will already be met when you create a 2-way (pairwise) set of Tests. You would only need to use this feature when ensuring that three or more specific values are tested together in a single test case. ## Import Forced Interactions You can import Forced Interactions, which allows you to upload data-driven Scenarios. > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content)
Support/Troubleshooting If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301501383).