An insurer's Dynamics 365 service copilot in the test environment still reads production cases. The team wants to treat the latest run as a valid test. What must change first?
Select an answer to reveal the explanation.
Short Explanation
A fire drill run inside the live office is not a drill, however short you make the checklist. You point the test service copilot at test cases before anyone calls a run on production cases a test. A shorter script on live cases is still a live run.
Full Explanation
A test counts as a test when the copilot and the cases it reads both belong to the test environment. This service copilot is still bound to production cases, so the latest run is exercising live work, and the first change is to point it at test cases before anyone treats that run as a valid test. Keeping the production cases and shortening the script only reduces how many live rows are touched; it does not give the team a test. Exporting those production cases to a spreadsheet and scoring the copilot from that sheet moves the live data into a file, and the file is still production content rather than test data. Publishing the test copilot into production so it shares a home with the live cases collapses the test environment into production, which is the opposite of separating the two. Exam caveat: realistic rows may be copied into the test environment; the line is which environment's cases the copilot is bound to, not whether the rows look familiar. Operational check: open the test copilot's data binding, confirm it resolves to the test case store, and rerun one scripted case that does not exist in production.