# 6. Report Management — Test Cases

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: report_management.md — every feature, sub-feature, and rule covered

---

## Test Execution Policy
- Zero tolerance: any deviation from documented behavior = FAILED = bug
- Every bug is immediately logged/reported (Bug ID, feature, sub-feature,
  expected vs actual, severity) and fixed 100% before the group passes
- Feature group passes only at 100% test pass rate

## Coverage Matrix
| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 6.1 Generate Reports on Demand | Report: the report (the report, the report, the type, the parameters, the period) | TC-SA-19-06-001 |
| 6.1 Generate Reports on Demand | Report type: the type (the type of the report, e.g., the revenue, the user, the content) | TC-SA-19-06-002 |
| 6.1 Generate Reports on Demand | Report parameters: the parameters (the parameters of the report, the filters, the scope) | TC-SA-19-06-003 |
| 6.1 Generate Reports on Demand | Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual) | TC-SA-19-06-004 |
| 6.1 Generate Reports on Demand | Report generation: the generation (the generation of the report, the time, the status) | TC-SA-19-06-005 |
| 6.1 Generate Reports on Demand | Report view: the view (the report, the type, the parameters, the period) | TC-SA-19-06-006 |
| 6.1 Generate Reports on Demand | Report export: the export (the report, the format, the period) | TC-SA-19-06-007 |
| 6.1 Generate Reports on Demand | Audit logging of the report generation | TC-SA-19-06-008 |
| 6.1 Generate Reports on Demand | Rule: the report is the output (the report, the type, the parameters, the period); the report is the result | TC-SA-19-06-001 |
| 6.1 Generate Reports on Demand | Rule: the report type is the category (the type of the report, e.g., the revenue, the user, the content); the type is the segment | TC-SA-19-06-002 |
| 6.1 Generate Reports on Demand | Rule: the report parameters are the controls (the parameters of the report, the filters, the scope); the parameters are the inputs | TC-SA-19-06-003 |
| 6.1 Generate Reports on Demand | Rule: the report period is the scope (the period of the report, e.g., the monthly, the quarterly, the annual); the period is the control | TC-SA-19-06-004 |
| 6.1 Generate Reports on Demand | Rule: the report is available (the report, the type, the parameters, the period); the generation is managed | TC-SA-19-06-006 |
| 6.1 Generate Reports on Demand | Rule: report generation is audit-logged with the report, period, and timestamp | TC-SA-19-06-008 |
| 6.2 Scheduled Report Generation | Schedule: the schedule (the schedule, the schedule, the report, the frequency, the time) | TC-SA-19-06-009 |
| 6.2 Scheduled Report Generation | Report: the report (the report, the report, the type, the parameters, the period) | TC-SA-19-06-010 |
| 6.2 Scheduled Report Generation | Frequency: the frequency (the frequency of the schedule, e.g., the daily, the weekly, the monthly) | TC-SA-19-06-011 |
| 6.2 Scheduled Report Generation | Schedule time: the time (the time of the schedule, the hour, the day) | TC-SA-19-06-012 |
| 6.2 Scheduled Report Generation | Schedule status: the status (the active, the paused, the completed) | TC-SA-19-06-013 |
| 6.2 Scheduled Report Generation | Schedule delivery: the delivery (the delivery of the report, the recipient, the method) | TC-SA-19-06-014 |
| 6.2 Scheduled Report Generation | Schedule view: the view (the schedules, the reports, the frequencies, the times) | TC-SA-19-06-015 |
| 6.2 Scheduled Report Generation | Audit logging of the schedule configuration | TC-SA-19-06-016 |
| 6.2 Scheduled Report Generation | Rule: the schedule is the automation (the schedule, the report, the frequency, the time); the schedule is the plan | TC-SA-19-06-009 |
| 6.2 Scheduled Report Generation | Rule: the report is the output (the report, the type, the parameters, the period); the report is the result | TC-SA-19-06-010 |
| 6.2 Scheduled Report Generation | Rule: the frequency is the cadence (the frequency of the schedule, e.g., the daily, the weekly, the monthly); the frequency is the rhythm | TC-SA-19-06-011 |
| 6.2 Scheduled Report Generation | Rule: the schedule status is the state (the active, the paused, the completed); the status is the control | TC-SA-19-06-013 |
| 6.2 Scheduled Report Generation | Rule: the schedule is set (the schedules, the reports, the frequencies, the times); the automation is managed | TC-SA-19-06-015 |
| 6.2 Scheduled Report Generation | Rule: schedule configuration is audit-logged with the schedule, frequency, and timestamp | TC-SA-19-06-016 |
| 6.3 Export Reports (Downloadable Formats) | Report: the report (the report, the report, the type, the format, the period) | TC-SA-19-06-017 |
| 6.3 Export Reports (Downloadable Formats) | Report type: the type (the type of the report, e.g., the revenue, the user, the content) | TC-SA-19-06-018 |
| 6.3 Export Reports (Downloadable Formats) | Report format: the format (the format of the report, e.g., the CSV, the Excel, the PDF) | TC-SA-19-06-019 |
| 6.3 Export Reports (Downloadable Formats) | Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual) | TC-SA-19-06-020 |
| 6.3 Export Reports (Downloadable Formats) | Report download: the download (the download of the report, the file, the size) | TC-SA-19-06-021 |
| 6.3 Export Reports (Downloadable Formats) | Report share: the share (the share of the report, the recipient, the method) | TC-SA-19-06-022 |
| 6.3 Export Reports (Downloadable Formats) | Report view: the view (the reports, the types, the formats, the period) | TC-SA-19-06-023 |
| 6.3 Export Reports (Downloadable Formats) | Audit logging of the report export | TC-SA-19-06-024 |
| 6.3 Export Reports (Downloadable Formats) | Rule: the report is the output (the report, the type, the format, the period); the report is the result | TC-SA-19-06-017 |
| 6.3 Export Reports (Downloadable Formats) | Rule: the report type is the category (the type of the report, e.g., the revenue, the user, the content); the type is the segment | TC-SA-19-06-018 |
| 6.3 Export Reports (Downloadable Formats) | Rule: the report format is the shape (the format of the report, e.g., the CSV, the Excel, the PDF); the format is the container | TC-SA-19-06-019 |
| 6.3 Export Reports (Downloadable Formats) | Rule: the report download is the action (the download of the report, the file, the size); the download is the retrieval | TC-SA-19-06-021 |
| 6.3 Export Reports (Downloadable Formats) | Rule: the report is available (the reports, the types, the formats, the period); the export is managed | TC-SA-19-06-023 |
| 6.3 Export Reports (Downloadable Formats) | Rule: report export is audit-logged with the report, format, and timestamp | TC-SA-19-06-024 |
| 6.4 Save and Reuse Report Configurations | Configuration: the configuration (the configuration, the configuration, the report, the parameters, the period) | TC-SA-19-06-025 |
| 6.4 Save and Reuse Report Configurations | Report: the report (the report, the report, the type, the parameters, the period) | TC-SA-19-06-026 |
| 6.4 Save and Reuse Report Configurations | Configuration name: the name (the name of the configuration, the label) | TC-SA-19-06-027 |
| 6.4 Save and Reuse Report Configurations | Configuration parameters: the parameters (the parameters of the configuration, the filters, the scope) | TC-SA-19-06-028 |
| 6.4 Save and Reuse Report Configurations | Configuration period: the period (the period of the configuration, e.g., the monthly, the quarterly, the annual) | TC-SA-19-06-029 |
| 6.4 Save and Reuse Report Configurations | Configuration reuse: the reuse (the reuse of the configuration, the report, the time) | TC-SA-19-06-030 |
| 6.4 Save and Reuse Report Configurations | Configuration view: the view (the configurations, the reports, the parameters, the period) | TC-SA-19-06-031 |
| 6.4 Save and Reuse Report Configurations | Audit logging of the configuration save and reuse | TC-SA-19-06-032 |
| 6.4 Save and Reuse Report Configurations | Rule: the configuration is the memory (the configuration, the report, the parameters, the period); the configuration is the template | TC-SA-19-06-025 |
| 6.4 Save and Reuse Report Configurations | Rule: the report is the output (the report, the type, the parameters, the period); the report is the result | TC-SA-19-06-026 |
| 6.4 Save and Reuse Report Configurations | Rule: the configuration name is the identifier (the name of the configuration, the label); the name is the label | TC-SA-19-06-027 |
| 6.4 Save and Reuse Report Configurations | Rule: the configuration reuse is the shortcut (the reuse of the configuration, the report, the time); the reuse is the action | TC-SA-19-06-030 |
| 6.4 Save and Reuse Report Configurations | Rule: the configuration is available (the configurations, the reports, the parameters, the period); the save is managed | TC-SA-19-06-031 |
| 6.4 Save and Reuse Report Configurations | Rule: configuration save and reuse is audit-logged with the configuration, period, and timestamp | TC-SA-19-06-032 |

## 6.1 Generate Reports on Demand

### TC-SA-19-06-001 — Report: the report (the report, the report, the type, the parameters, the period); the report is the result
**Type:** Positive
**Covers:** 6.1 → Report: the report (the report, the report, the type, the parameters, the period); Rule: the report is the output (the report, the type, the parameters, the period); the report is the result
**Preconditions:** Super Admin is logged in; report data exists.
**Steps:**
1. Open Custom Reporting → Report Management → Generate Reports on Demand.
2. Generate a report: the report (the report, the report, the type, the parameters, the period) — verify the report is the output.
3. Verify the report shows the type, the parameters, and the period.
4. Verify the report data is accurate for the selection.
**Expected Result:** The report is generated — the report, the type, the parameters, and the period are the result.
**Priority:** Critical

### TC-SA-19-06-002 — Report type: the type (the type of the report, e.g., the revenue, the user, the content); the type is the segment
**Type:** Positive
**Covers:** 6.1 → Report type: the type (the type of the report, e.g., the revenue, the user, the content); Rule: the report type is the category (the type of the report, e.g., the revenue, the user, the content); the type is the segment
**Preconditions:** Report data exists for multiple report types.
**Steps:**
1. Select the report types: the type (the type of the report, e.g., the revenue, the user, the content) — verify the type is the category.
2. Verify each type generates the correct report.
3. Verify the report content matches the selected type.
**Expected Result:** The report type is selected — the type of the report (the revenue, the user, the content) is the segment.
**Priority:** High

### TC-SA-19-06-003 — Report parameters: the parameters (the parameters of the report, the filters, the scope); the parameters are the inputs
**Type:** Positive
**Covers:** 6.1 → Report parameters: the parameters (the parameters of the report, the filters, the scope); Rule: the report parameters are the controls (the parameters of the report, the filters, the scope); the parameters are the inputs
**Preconditions:** Report data exists across multiple filters and scopes.
**Steps:**
1. Set the report parameters: the parameters (the parameters of the report, the filters, the scope) — verify the parameters are the controls.
2. Apply filters (e.g., by course, by region) — verify the report narrows to the filtered data.
3. Verify the report reflects the applied parameters exactly.
**Expected Result:** The report parameters are set — the parameters of the report, the filters, and the scope are the inputs.
**Priority:** High

### TC-SA-19-06-004 — Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual); the period is the control
**Type:** Positive
**Covers:** 6.1 → Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual); Rule: the report period is the scope (the period of the report, e.g., the monthly, the quarterly, the annual); the period is the control
**Preconditions:** Report data exists across monthly, quarterly, and annual periods.
**Steps:**
1. Set the report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual) — verify the period is the scope.
2. Switch between monthly, quarterly, and annual — verify the report updates for each period.
3. Verify each period covers the correct date range.
**Expected Result:** The report period is set — the period of the report (the monthly, the quarterly, the annual) is the control.
**Priority:** High

### TC-SA-19-06-005 — Report generation: the generation (the generation of the report, the time, the status); the generation is the process
**Type:** Edge
**Covers:** 6.1 → Report generation: the generation (the generation of the report, the time, the status)
**Preconditions:** Report data exists; a very large report (performance edge) and a report with no matching data (empty edge) are also prepared.
**Steps:**
1. Generate a report: the generation (the generation of the report, the time, the status) — verify the generation is the process.
2. Verify the generation shows the time and the status (generating → completed).
3. Generate the very large report — verify it completes without timeout; generate the empty report — verify an empty-state message (no error).
**Expected Result:** The report generation works — the generation of the report, the time, and the status are the process; large and empty reports are handled.
**Priority:** High

### TC-SA-19-06-006 — Report view: the view (the report, the type, the parameters, the period); the generation is managed
**Type:** Positive
**Covers:** 6.1 → Report view: the view (the report, the type, the parameters, the period); Rule: the report is available (the report, the type, the parameters, the period); the generation is managed
**Preconditions:** A report has been generated.
**Steps:**
1. View the report: the view (the report, the type, the parameters, the period) — verify the report is available.
2. Verify the view shows the type, the parameters, and the period.
3. Verify the report data is displayed correctly.
**Expected Result:** The report is viewed — the report, the type, the parameters, and the period are available; the generation is managed.
**Priority:** High

### TC-SA-19-06-007 — Report export: the export (the report, the format, the period); the export is the record
**Type:** Positive
**Covers:** 6.1 → Report export: the export (the report, the format, the period)
**Preconditions:** A report has been generated.
**Steps:**
1. Export the report: the export (the report, the format, the period).
2. Verify the export is generated in the selected format.
3. Verify the exported data matches the report.
**Expected Result:** The report is exported — the report in the selected format for the period is generated.
**Priority:** Medium

### TC-SA-19-06-008 — Report generation is audit-logged with the report, period, and timestamp
**Type:** Positive
**Covers:** 6.1 → Audit logging of the report generation; Rule: report generation is audit-logged with the report, period, and timestamp
**Preconditions:** Super Admin has generated a report on demand.
**Steps:**
1. Open the audit trail and filter by "report generation".
2. Verify entries show the report, the period, and the timestamp.
**Expected Result:** The report generation is audit-logged with the report, period, and timestamp.
**Priority:** Critical

## 6.2 Scheduled Report Generation

### TC-SA-19-06-009 — Schedule: the schedule (the schedule, the schedule, the report, the frequency, the time); the schedule is the plan
**Type:** Positive
**Covers:** 6.2 → Schedule: the schedule (the schedule, the schedule, the report, the frequency, the time); Rule: the schedule is the automation (the schedule, the report, the frequency, the time); the schedule is the plan
**Preconditions:** Super Admin is logged in; report data exists.
**Steps:**
1. Open Custom Reporting → Report Management → Scheduled Report Generation.
2. Create a schedule: the schedule (the schedule, the schedule, the report, the frequency, the time) — verify the schedule is the automation.
3. Verify the schedule shows the report, the frequency, and the time.
4. Wait for the scheduled time — verify the report is generated automatically.
**Expected Result:** The schedule is created — the schedule, the report, the frequency, and the time are the plan; the report is generated automatically.
**Priority:** Critical

### TC-SA-19-06-010 — Report: the report (the report, the report, the type, the parameters, the period); the report is the result
**Type:** Positive
**Covers:** 6.2 → Report: the report (the report, the report, the type, the parameters, the period); Rule: the report is the output (the report, the type, the parameters, the period); the report is the result
**Preconditions:** A schedule is being created.
**Steps:**
1. Select the report for the schedule: the report (the report, the report, the type, the parameters, the period) — verify the report is the output.
2. Verify the report shows the type, the parameters, and the period.
3. Verify the scheduled report generates the correct content.
**Expected Result:** The report is selected — the report, the type, the parameters, and the period are the result.
**Priority:** High

### TC-SA-19-06-011 — Frequency: the frequency (the frequency of the schedule, e.g., the daily, the weekly, the monthly); the frequency is the rhythm
**Type:** Positive
**Covers:** 6.2 → Frequency: the frequency (the frequency of the schedule, e.g., the daily, the weekly, the monthly); Rule: the frequency is the cadence (the frequency of the schedule, e.g., the daily, the weekly, the monthly); the frequency is the rhythm
**Preconditions:** A schedule is being created.
**Steps:**
1. Set the frequency: the frequency (the frequency of the schedule, e.g., the daily, the weekly, the monthly) — verify the frequency is the cadence.
2. Create schedules with daily, weekly, and monthly frequencies — verify each fires at the correct cadence.
3. Verify the frequency is shown on the schedule.
**Expected Result:** The frequency is set — the frequency of the schedule (the daily, the weekly, the monthly) is the rhythm.
**Priority:** High

### TC-SA-19-06-012 — Schedule time: the time (the time of the schedule, the hour, the day); the time is the trigger
**Type:** Positive
**Covers:** 6.2 → Schedule time: the time (the time of the schedule, the hour, the day)
**Preconditions:** A schedule is being created.
**Steps:**
1. Set the schedule time: the time (the time of the schedule, the hour, the day) — verify the time is the trigger.
2. Verify the schedule fires at the exact hour and day.
3. Verify the time is shown on the schedule.
**Expected Result:** The schedule time is set — the time of the schedule, the hour, and the day are the trigger.
**Priority:** High

### TC-SA-19-06-013 — Schedule status: the status (the active, the paused, the completed); the status is the control
**Type:** Positive
**Covers:** 6.2 → Schedule status: the status (the active, the paused, the completed); Rule: the schedule status is the state (the active, the paused, the completed); the status is the control
**Preconditions:** Schedules with active, paused, and completed statuses exist.
**Steps:**
1. View the schedule status: the status (the active, the paused, the completed) — verify the status is the state.
2. Pause an active schedule — verify it stops generating; resume it — verify it resumes.
3. Verify a completed schedule shows the completed status.
**Expected Result:** The schedule status is shown — the active, the paused, and the completed are the control.
**Priority:** High

### TC-SA-19-06-014 — Schedule delivery: the delivery (the delivery of the report, the recipient, the method); the delivery is the transfer
**Type:** Positive
**Covers:** 6.2 → Schedule delivery: the delivery (the delivery of the report, the recipient, the method)
**Preconditions:** A schedule is configured with a recipient and method.
**Steps:**
1. Configure the schedule delivery: the delivery (the delivery of the report, the recipient, the method) — verify the delivery is the transfer.
2. Wait for the scheduled time — verify the report is delivered to the recipient via the method.
3. Verify the recipient receives the report correctly.
**Expected Result:** The schedule delivery works — the delivery of the report to the recipient via the method is the transfer.
**Priority:** High

### TC-SA-19-06-015 — Schedule view: the view (the schedules, the reports, the frequencies, the times); the automation is managed
**Type:** Positive
**Covers:** 6.2 → Schedule view: the view (the schedules, the reports, the frequencies, the times); Rule: the schedule is set (the schedules, the reports, the frequencies, the times); the automation is managed
**Preconditions:** Multiple schedules exist.
**Steps:**
1. View the schedules: the view (the schedules, the reports, the frequencies, the times) — verify the schedule is set.
2. Verify each schedule shows the report, the frequency, and the time.
3. Verify the automation is managed (create, pause, resume, delete).
**Expected Result:** The schedules are viewed — the schedules, the reports, the frequencies, and the times are set; the automation is managed.
**Priority:** High

### TC-SA-19-06-016 — Schedule configuration is audit-logged with the schedule, frequency, and timestamp
**Type:** Positive
**Covers:** 6.2 → Audit logging of the schedule configuration; Rule: schedule configuration is audit-logged with the schedule, frequency, and timestamp
**Preconditions:** Super Admin has configured a schedule.
**Steps:**
1. Open the audit trail and filter by "schedule".
2. Verify entries show the schedule, the frequency, and the timestamp.
**Expected Result:** The schedule configuration is audit-logged with the schedule, frequency, and timestamp.
**Priority:** Critical

## 6.3 Export Reports (Downloadable Formats)

### TC-SA-19-06-017 — Report: the report (the report, the report, the type, the format, the period); the report is the result
**Type:** Positive
**Covers:** 6.3 → Report: the report (the report, the report, the type, the format, the period); Rule: the report is the output (the report, the type, the format, the period); the report is the result
**Preconditions:** Super Admin is logged in; a report is available for export.
**Steps:**
1. Open Custom Reporting → Report Management → Export Reports.
2. Select the report: the report (the report, the report, the type, the format, the period) — verify the report is the output.
3. Verify the report shows the type, the format, and the period.
**Expected Result:** The report is selected — the report, the type, the format, and the period are the result.
**Priority:** Critical

### TC-SA-19-06-018 — Report type: the type (the type of the report, e.g., the revenue, the user, the content); the type is the segment
**Type:** Positive
**Covers:** 6.3 → Report type: the type (the type of the report, e.g., the revenue, the user, the content); Rule: the report type is the category (the type of the report, e.g., the revenue, the user, the content); the type is the segment
**Preconditions:** Reports of multiple types exist.
**Steps:**
1. Select the report types: the type (the type of the report, e.g., the revenue, the user, the content) — verify the type is the category.
2. Verify each type can be exported.
3. Verify the exported content matches the selected type.
**Expected Result:** The report type is selected — the type of the report (the revenue, the user, the content) is the segment.
**Priority:** High

### TC-SA-19-06-019 — Report format: the format (the format of the report, e.g., the CSV, the Excel, the PDF); the format is the container
**Type:** Positive
**Covers:** 6.3 → Report format: the format (the format of the report, e.g., the CSV, the Excel, the PDF); Rule: the report format is the shape (the format of the report, e.g., the CSV, the Excel, the PDF); the format is the container
**Preconditions:** A report is available for export.
**Steps:**
1. Select the report format: the format (the format of the report, e.g., the CSV, the Excel, the PDF) — verify the format is the shape.
2. Export in each format (CSV, Excel, PDF) — verify each is generated correctly.
3. Verify the exported files open and display the report correctly.
**Expected Result:** The report format is selected — the format of the report (the CSV, the Excel, the PDF) is the container.
**Priority:** High

### TC-SA-19-06-020 — Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual); the period is the scope
**Type:** Positive
**Covers:** 6.3 → Report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual)
**Preconditions:** Report data exists across monthly, quarterly, and annual periods.
**Steps:**
1. Set the report period: the period (the period of the report, e.g., the monthly, the quarterly, the annual) — verify the period is the scope.
2. Switch between monthly, quarterly, and annual — verify the report updates for each period.
3. Verify each period covers the correct date range.
**Expected Result:** The report period is set — the period of the report (the monthly, the quarterly, the annual) is the scope.
**Priority:** High

### TC-SA-19-06-021 — Report download: the download (the download of the report, the file, the size); the download is the retrieval
**Type:** Edge
**Covers:** 6.3 → Report download: the download (the download of the report, the file, the size); Rule: the report download is the action (the download of the report, the file, the size); the download is the retrieval
**Preconditions:** A report is ready for download; a very large report (size edge) is also prepared.
**Steps:**
1. Download the report: the download (the download of the report, the file, the size) — verify the download is the action.
2. Verify the file is downloaded with the correct size.
3. Download the very large report — verify it completes without corruption or timeout.
**Expected Result:** The report is downloaded — the download of the report, the file, and the size are the retrieval; a large report is handled.
**Priority:** High

### TC-SA-19-06-022 — Report share: the share (the share of the report, the recipient, the method); the share is the transfer
**Type:** Positive
**Covers:** 6.3 → Report share: the share (the share of the report, the recipient, the method)
**Preconditions:** A report is ready to share.
**Steps:**
1. Share the report: the share (the share of the report, the recipient, the method) — verify the share is the transfer.
2. Verify the report is shared with the recipient via the method.
3. Verify the recipient receives the report correctly.
**Expected Result:** The report is shared — the share of the report to the recipient via the method is the transfer.
**Priority:** High

### TC-SA-19-06-023 — Report view: the view (the reports, the types, the formats, the period); the export is managed
**Type:** Positive
**Covers:** 6.3 → Report view: the view (the reports, the types, the formats, the period); Rule: the report is available (the reports, the types, the formats, the period); the export is managed
**Preconditions:** Multiple reports exist.
**Steps:**
1. View the reports: the view (the reports, the types, the formats, the period) — verify the report is available.
2. Verify each report shows the type, the format, and the period.
3. Verify the export is managed (export, download, share).
**Expected Result:** The reports are viewed — the reports, the types, the formats, and the period are available; the export is managed.
**Priority:** High

### TC-SA-19-06-024 — Report export is audit-logged with the report, format, and timestamp
**Type:** Positive
**Covers:** 6.3 → Audit logging of the report export; Rule: report export is audit-logged with the report, format, and timestamp
**Preconditions:** Super Admin has exported a report.
**Steps:**
1. Open the audit trail and filter by "report export".
2. Verify entries show the report, the format, and the timestamp.
**Expected Result:** The report export is audit-logged with the report, format, and timestamp.
**Priority:** Critical

## 6.4 Save and Reuse Report Configurations

### TC-SA-19-06-025 — Configuration: the configuration (the configuration, the configuration, the report, the parameters, the period); the configuration is the template
**Type:** Positive
**Covers:** 6.4 → Configuration: the configuration (the configuration, the configuration, the report, the parameters, the period); Rule: the configuration is the memory (the configuration, the report, the parameters, the period); the configuration is the template
**Preconditions:** Super Admin is logged in; a report has been generated with parameters.
**Steps:**
1. Open Custom Reporting → Report Management → Save and Reuse Report Configurations.
2. Save the configuration: the configuration (the configuration, the configuration, the report, the parameters, the period) — verify the configuration is the memory.
3. Verify the configuration shows the report, the parameters, and the period.
**Expected Result:** The configuration is saved — the configuration, the report, the parameters, and the period are the template.
**Priority:** Critical

### TC-SA-19-06-026 — Report: the report (the report, the report, the type, the parameters, the period); the report is the result
**Type:** Positive
**Covers:** 6.4 → Report: the report (the report, the report, the type, the parameters, the period); Rule: the report is the output (the report, the type, the parameters, the period); the report is the result
**Preconditions:** A configuration is being saved.
**Steps:**
1. Select the report for the configuration: the report (the report, the report, the type, the parameters, the period) — verify the report is the output.
2. Verify the report shows the type, the parameters, and the period.
3. Verify the configuration captures the report correctly.
**Expected Result:** The report is selected — the report, the type, the parameters, and the period are the result.
**Priority:** High

### TC-SA-19-06-027 — Configuration name: the name (the name of the configuration, the label); the name is the label
**Type:** Edge
**Covers:** 6.4 → Configuration name: the name (the name of the configuration, the label); Rule: the configuration name is the identifier (the name of the configuration, the label); the name is the label
**Preconditions:** A configuration is being saved; an existing configuration with the same name (duplicate edge) also exists.
**Steps:**
1. Enter the configuration name: the name (the name of the configuration, the label) — verify the name is the identifier.
2. Save the configuration — verify the name is shown on the configuration.
3. Try to save another configuration with the same name — verify the duplicate is handled (blocked or auto-suffixed, no silent overwrite).
**Expected Result:** The configuration name is set — the name of the configuration and the label are the identifier; duplicates are handled.
**Priority:** High

### TC-SA-19-06-028 — Configuration parameters: the parameters (the parameters of the configuration, the filters, the scope); the parameters are the inputs
**Type:** Positive
**Covers:** 6.4 → Configuration parameters: the parameters (the parameters of the configuration, the filters, the scope)
**Preconditions:** A configuration is being saved with filters and scope.
**Steps:**
1. Set the configuration parameters: the parameters (the parameters of the configuration, the filters, the scope) — verify the parameters are the controls.
2. Verify the parameters are captured in the configuration.
3. Reuse the configuration — verify the parameters are applied exactly.
**Expected Result:** The configuration parameters are set — the parameters of the configuration, the filters, and the scope are the inputs.
**Priority:** High

### TC-SA-19-06-029 — Configuration period: the period (the period of the configuration, e.g., the monthly, the quarterly, the annual); the period is the scope
**Type:** Positive
**Covers:** 6.4 → Configuration period: the period (the period of the configuration, e.g., the monthly, the quarterly, the annual)
**Preconditions:** A configuration is being saved.
**Steps:**
1. Set the configuration period: the period (the period of the configuration, e.g., the monthly, the quarterly, the annual) — verify the period is the scope.
2. Verify the period is captured in the configuration.
3. Reuse the configuration — verify the period is applied exactly.
**Expected Result:** The configuration period is set — the period of the configuration (the monthly, the quarterly, the annual) is the scope.
**Priority:** High

### TC-SA-19-06-030 — Configuration reuse: the reuse (the reuse of the configuration, the report, the time); the reuse is the action
**Type:** Positive
**Covers:** 6.4 → Configuration reuse: the reuse (the reuse of the configuration, the report, the time); Rule: the configuration reuse is the shortcut (the reuse of the configuration, the report, the time); the reuse is the action
**Preconditions:** A configuration has been saved.
**Steps:**
1. Reuse the configuration: the reuse (the reuse of the configuration, the report, the time) — verify the reuse is the shortcut.
2. Verify the report is regenerated with the saved parameters and period.
3. Verify the reuse takes less time than re-entering the parameters manually.
**Expected Result:** The configuration is reused — the reuse of the configuration, the report, and the time are the action.
**Priority:** High

### TC-SA-19-06-031 — Configuration view: the view (the configurations, the reports, the parameters, the period); the save is managed
**Type:** Positive
**Covers:** 6.4 → Configuration view: the view (the configurations, the reports, the parameters, the period); Rule: the configuration is available (the configurations, the reports, the parameters, the period); the save is managed
**Preconditions:** Multiple configurations exist.
**Steps:**
1. View the configurations: the view (the configurations, the reports, the parameters, the period) — verify the configuration is available.
2. Verify each configuration shows the report, the parameters, and the period.
3. Verify the save is managed (save, reuse, delete).
**Expected Result:** The configurations are viewed — the configurations, the reports, the parameters, and the period are available; the save is managed.
**Priority:** High

### TC-SA-19-06-032 — Configuration save and reuse is audit-logged with the configuration, period, and timestamp
**Type:** Positive
**Covers:** 6.4 → Audit logging of the configuration save and reuse; Rule: configuration save and reuse is audit-logged with the configuration, period, and timestamp
**Preconditions:** Super Admin has saved and reused a configuration.
**Steps:**
1. Open the audit trail and filter by "configuration".
2. Verify entries show the configuration, the period, and the timestamp for both save and reuse.
**Expected Result:** The configuration save and reuse is audit-logged with the configuration, period, and timestamp.
**Priority:** Critical