---
title: Validation & Testing
slug: validation-and-testing
createdAt: 2025-10-29T21:30:32.862Z
---

Thorough validation ensures each connector behaves predictably and avoids unintended bulk changes.

# Pre-deployment Checks

- Confirm the **schema** matches the source data — all required columns exist and are typed correctly.&#x20;
- Validate **key fields** for uniqueness in the source.&#x20;
- Review **delete strategy** (flagged vs. result-set) to confirm it aligns with data behaviour.&#x20;
- Ensure **history logging** is enabled for traceability.&#x20;

# Dry Runs

1. Set processImport/maxChanges and processImport/maxDelete to low values (e.g., 50).&#x20;
2. Import a small data subset.&#x20;
3. Verify that detected changes appear in the **connector data table** with expected Action states.&#x20;
4. Review **pending changes** in the web interface before running the process step.&#x20;

# Functional Testing

- Validate that **creates, updates, and deletes** trigger the correct event handlers.&#x20;
- Check that scripts, job submissions, and notifications execute as expected.&#x20;
- Confirm that multi-value and foreign key columns are parsed correctly.&#x20;
- Review that role or user links resolve properly via the relevant link handlers.&#x20;

# Error Testing

- Simulate missing or malformed data to confirm retries and error handling work.&#x20;
- Verify that email notifications fire on error conditions.&#x20;
- Confirm that connectors stop gracefully when exceeding maxDelete or maxChanges thresholds.&#x20;

# Post-deployment Monitoring

- Review **history tables** after each run to confirm change tracking.&#x20;
- Monitor **connector logs** for warnings or retries.&#x20;
- Spot-check **sample rows** across the import, data, and history tables.&#x20;
- Schedule automated notifications on failure conditions.&#x20;
