What strategies do you use to manage, update, and interpret large databases of test results and log files?
For this SQL exercise, summarize test executions and their associated log records for January 2025. Include only test suites with at least one failed execution.
suite_name, total_executions, failed_executions, executions_with_errors, and total_log_entries.suite_name ascending.| Column | Type | Description |
|---|---|---|
| test_result_idPK | INT | Unique test-result identifier |
| execution_id | VARCHAR(30) | Identifier shared by a test execution and its logs |
| suite_name | VARCHAR(100) | Name of the test suite |
| status | VARCHAR(20) | Execution status |
| executed_at | TIMESTAMP | Timestamp when the test execution completed |
| Column | Type | Description |
|---|---|---|
| log_idPK | INT | Unique log-record identifier |
| execution_id | VARCHAR(30) | Related test execution identifier |
| severity | VARCHAR(20) | Log severity level |
| log_message | TEXT | Captured log message |