If records are modified while a test is running in the same session, what happens to those changes after the test completes?

When a test is running in ServiceNow, it often executes within a specific transaction that can be isolated from other operations. This transaction management ensures that any modifications made to records during the testing process do not affect the actual data in the database until the test completes successfully.

If records are modified while the test is running, all those changes are made in a temporary context. Once the test concludes, if everything runs as intended, the changes can either be committed or reverted based on the test outcome and the specific transaction handling defined in the testing framework. However, in the scenario outlined, where changes are made during the test, they would typically be rolled back after the test completes. This rollback mechanism prevents any unintended side effects from corrupting the data integrity, thereby ensuring that test runs are clean and do not interfere with the normal operations of the system.

The other options would not accurately reflect how ServiceNow manages transactions during testing. Changes being saved would contradict the rollback principle that protects the database. Saying there’s no effect on records would overlook the transaction mechanisms in place, and suggesting a system crash implies a failure in the transaction handling, which is not typical behavior during a well-structured test.