Optimizer

Use this section to view frequently asked questions about Optimizer, including queries related to different prompts and their usage.

• Can Optimizer parameterize the hardcoded values found by the Hardcoded Test Data prompt? Ans: No. The Hardcoded Test Data prompt only identifies test cases and test step groups that use fixed values instead of data parameterization. Optimizer does not provide an action to fix these values. Review the listed test cases and update them manually.

• Can I modify the names suggested by the Non-compliant Names prompt before applying them? Ans: Yes. In the rename dialog, select Add text to add text before or after the suggested names. Before you confirm, review the Invalid reason column to understand which naming standard the current name does not meet. The same steps apply to other artifacts, such as test cases and execution lists.

• Does the Stalled Artifacts prompt flag artifacts that nobody has opened in 60 days? Ans: The prompt checks status, not access. It identifies Element Repositories, test cases, execution lists, and data tables whose status has not changed for more than 60 days. An artifact that users view regularly can still appear in the results if its status has not changed.

• Can I restore items deleted from Optimizer? Ans: No. Deletion from Optimizer is permanent, and Optimizer does not restore deleted items. Deleting an item can also affect existing test executions. Review the selected findings carefully before you confirm, especially when you use Delete All.

• Does the Frequently Terminated Tests prompt consider all past executions? Ans: No. The prompt considers only terminated runs in the last 30 days and lists the test cases with the highest number of terminations in that period. Terminations that happened earlier are not included.

• Does the Duplicated Execution Entries prompt remove duplicate test cases from the execution list? Ans: No. The prompt only identifies execution lists that contain the same test case more than once. Review the entries in the result table and remove the duplicate test cases from the execution list yourself.

• Do Custom prompts work the same way as Verified prompts? Ans: No. Verified prompts are predefined checks with fixed conditions. Custom prompts let you describe a requirement in your own words, such as "Analyze my test cases that nobody has run since June." Optimizer interprets the request and returns an Action Summary with a result table. Because an AI generates the results of Custom prompts, check them before acting, especially before deleting or modifying artifacts.

• Are the same filter options available for every prompt? Ans: No. The filter options depend on the selected prompt and the results it displays. Filters such as Project Name, Assigned To, and Status are available only when those fields apply to the findings in the result table.

• Can I find out who ran a prompt and when its findings changed? Ans: Yes. Select the Audit Logs icon beside Run on the prompt result page. The audit log records each prompt execution, including when the findings were updated and who started the execution. Use Date Range to show only the actions performed between specific dates, and expand a month to see the individual actions performed by users.

• Do the Action Summary and the Chart show the same results? Ans: Yes, in different forms. The Action Summary describes the conditions the prompt checked and the results it found, including the number of findings. The Chart shows a graphical summary of the same results, which helps you see the distribution of findings at a glance.

• Can I use search, filter, and column options on Custom prompt results? Ans: Yes. The Optimization page displays findings for both Verified and Custom prompts. You can use Search, Filter, Line Spacing, and Manage Columns on the result table of either prompt type.

• Does the Flaky Test Cases prompt evaluate every test case that has execution history? Ans: No. The prompt evaluates a test case only when it has at least 10 runs. It calculates flakiness using only the latest 10 runs, so earlier runs do not affect the result.

• Does the Contains Static Waits prompt consider static waits applied to all elements? Ans: No. The prompt considers only static waits applied to solid elements. Waits applied to other elements are not included in the results, so Replace all static waits and Replace selected static waits do not change them.

• Do all prompts require completed execution data? Ans: No. Execution data is required only for prompts that analyze test execution behavior, such as Flaky Test Cases, Step Runtime Outliers, Frequently Terminated Tests, and Runtime Regressions. Prompts that analyze project artifacts do not require completed executions.

• Can an artifact be identified as an orphaned artifact even though it exists in the project? Ans: Yes. The Orphaned Artifacts prompt checks the assignment status of supported artifacts. An artifact can exist in the project but still be identified when it has no assignee or its assigned user is inactive.

• Does Runtime Regressions analyze a single execution to detect a runtime increase? Ans: No. The prompt compares the last five completed runs. This identifies an increase in execution time across runs instead of treating the duration of a single run as a runtime change.

• Can a Custom prompt return results that differ from a Verified prompt covering a similar project area? Ans: Yes. Verified prompts use predefined conditions, while Custom prompts are based on the requirement expressed in the submitted query. Differences in the conditions can produce different result sets.