Do Custom Field Mappings Survive QTest Upgrade Failure and Backup Restore?

Question

QTest's documented upgrade recovery path relies on restoring a pre‑upgrade database and file‑system backup rather than an automatic rollback. The upgrade wizard does not revert schema changes or re‑apply custom configurations when it aborts mid‑process, leaving administrators to reconcile any partial updates manually.

A gap remains in the official guidance: it does not explicitly state whether custom field mappings and integration scripts—stored as metadata in the database and as files on disk—are fully preserved when a failed upgrade is followed by a backup restore. Community reports suggest these artifacts may be reset or require manual re‑import, but no authoritative source confirms the behavior across versions.

Which QTest versions have been verified to retain custom field mappings after a backup restore following a failed upgrade? Does the restore process also reinstate integration script files and their registered endpoints without additional steps? What verification steps does QTest support recommend to confirm that all customizations are intact before returning the system to production?

Tasadduq Burney · Answer

Persistence of Customizations During Restore
Yes, custom field mappings and integration scripts survive a failed upgrade provided that both the database and the file system are restored from a synchronized pre-upgrade backup. Because QTest does not provide an automatic rollback mechanism for failed upgrades, the integrity of your customizations depends entirely on the state of the backup images used for recovery.

Likely Behavior vs. Confirmed Facts
While a full restore typically returns the system to its previous state, there are critical distinctions in how different artifacts are handled:

Custom Field Mappings: These are stored as metadata within the database. A successful database restore will reinstate these mappings. However, if a restore is performed using a database backup that does not align with the file system state, orphaned references may occur.
  Integration Scripts: These exist as files on the application server disk. While the files themselves are preserved via a file-system restore, the registration of their endpoints within the application may require manual verification to ensure the link between the database metadata and the physical file remains intact.

Recovery and Verification Steps
To ensure the system is production-ready after a restore, follow these verification steps:

Validate Metadata: Access the QTest Admin UI and verify that custom field definitions are visible and mapped to the correct entities.
  Verify Disk Artifacts: Check the integration script directories on the application server. Confirm that file timestamps match the pre-upgrade backup date.
  Test Endpoints: Trigger a test execution of a registered integration script to confirm that the endpoint is still active and communicating with the target system.
  Audit Logs: Review the upgrade audit logs for any entries indicating partial schema modifications that may have occurred before the failure, ensuring no residual changes persist after the restore.

Required Diagnostic Detail
To provide a more definitive confirmation of behavior, please specify the exact version number of the QTest instance you are upgrading from and to, as metadata handling can vary between major releases.

Do Custom Field Mappings Survive QTest Upgrade Failure and Backup Restore?

1 answer

Persistence of Customizations During Restore

Likely Behavior vs. Confirmed Facts

Recovery and Verification Steps

Required Diagnostic Detail

Your perspective belongs here.

0 question comments