- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Which type of tests can user run to ensure if CMDB still work after upgrading or deploying of new application or integration ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
To ensure the CMDB (Configuration Management Database) still works properly after an upgrade or new application/integration deployment, users typically run a combination of the following tests:
1. Smoke / Sanity Testing
Quick, high-level checks to confirm that core CMDB functionality is still working.
Example: Can you view CIs, search records, and open related forms after deployment?
2. Regression Testing
Verify that existing features and processes haven’t broken after the upgrade or new integration.
Example: Discovery schedules still populate CI records correctly, CI relationships are intact.
3. Integration Testing
Validate that interconnected systems still communicate correctly with CMDB.
Example: Incident, change, or asset management modules still pull correct CI data; integrations with monitoring tools are intact.
4. Data Integrity / Validation Testing
Check for duplicate CIs, missing attributes, or broken relationships.
Example: CI relationships like parent-child or dependency links remain consistent after import or discovery.
5. Performance / Load Testing (Optional but recommended for major upgrades)
Ensure CMDB performance remains acceptable under normal and peak load.
Example: Queries, reports, and dashboards load within expected times.
6. End-to-End Scenario Testing
Test real-world processes that rely on CMDB data.
Example: Create an incident linked to a CI, trigger a change, verify updates propagate correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hi,
I would say this depends on how you define "CMDB still work".
What would you want to know here?
That the existing integrations are still working?
That the existing data is intact?
That correct data has been overwritten by the new app/integration?
Something else ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
To ensure the CMDB (Configuration Management Database) still works properly after an upgrade or new application/integration deployment, users typically run a combination of the following tests:
1. Smoke / Sanity Testing
Quick, high-level checks to confirm that core CMDB functionality is still working.
Example: Can you view CIs, search records, and open related forms after deployment?
2. Regression Testing
Verify that existing features and processes haven’t broken after the upgrade or new integration.
Example: Discovery schedules still populate CI records correctly, CI relationships are intact.
3. Integration Testing
Validate that interconnected systems still communicate correctly with CMDB.
Example: Incident, change, or asset management modules still pull correct CI data; integrations with monitoring tools are intact.
4. Data Integrity / Validation Testing
Check for duplicate CIs, missing attributes, or broken relationships.
Example: CI relationships like parent-child or dependency links remain consistent after import or discovery.
5. Performance / Load Testing (Optional but recommended for major upgrades)
Ensure CMDB performance remains acceptable under normal and peak load.
Example: Queries, reports, and dashboards load within expected times.
6. End-to-End Scenario Testing
Test real-world processes that rely on CMDB data.
Example: Create an incident linked to a CI, trigger a change, verify updates propagate correctly.
