DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Test Case ID | Test Objective | Test Steps | Expected Outcome | Test Type | Execution Status |
|---|---|---|---|---|---|
AIP78_TC_001 | Verify user can create a backfill using /public/backfill endpoint | 1. Send a POST request to create a backfill job for a specific DAG using API with valid parameters. { |
| Positive | Pass |
AIP78_TC_002 | Verify user is able to create backfills for different time ranges | 1. Create multiple backfill jobs for the same DAG using different combinations of start_date and end_date via API. | Backfill jobs are created successfully with the correct time ranges. | Positive | Pass |
AIP78_TC_003 | Verify user is still able to run backfills using CLI | 1. Run the backfill command using CLI for a specific DAG with valid parameters. | CLI backfill runs successfully with only the supported parameters. | Positive | Pass |
AIP78_TC_004 | Verify user is able to perform a dry run using backfill dry_run endpoint |
|
| Positive | Pass |
AIP78_TC_005 | Verify user can create, monitor, clear, and manage backfill jobs from UI | 1. Create a backfill job from the API or CLI. | Users can create, monitor, and manage backfill jobs from the UI without issues. | Not Implemented | |
AIP78_TC_006 | Verify BackfillRunDagRun table correctly maps Backfill job with DAG run | 1. Create a backfill job and verify entries in the BackfillRunDagRun table. | BackfillRunDagRun table correctly maps each backfill job with the appropriate DAG runs. | Positive | Pass |
AIP78_TC_007 | Verify backfill DAG runs respect concurrency limitations | 1. Create a backfill job with multiple DAG runs. | Backfill DAG runs are created and managed within defined concurrency limitations. | Positive | Pass |
AIP78_TC_008 | Perform scheduler benchmarking (task throughput tests) | 1. Run backfill jobs under different scenarios (e.g., large backfill range, high number of tasks). | Scheduler maintains acceptable performance under increased load due to backfill jobs. | Performance | Pass |
AIP78_TC_009 | Verify backfills for different types of DAGs (using dynamic mapping, datasets, setup & teardown, etc.) | 1. Create backfill jobs for different types of DAGs (e.g., dynamic mapped tasks, setup & teardown tasks). | Backfill jobs work correctly with various DAG types without errors. | Positive | Pass |
AIP78_TC_010 | Verify user can list backfill using List backfill endpoint. |
| All the backfill details listed in response from the backfill table | Positive | Pass |
AIP78_TC_011 | Verify user can get details of specific backfill ID |
| Details of a specific backfill id are listed in the backfill table | Positive | Pass |
AIP78_TC_012 | Verify user can pause running backfill |
| Running backfills should be paused successfully | Positive | Pass |
AIP78_TC_013 | Verify user can unpause running backfill |
| Paused backfills should be resumed successfully | Positive | Pass |
AIP78_TC_014 | Verify user can cancel running backfill |
| Backfill should be cancelled successfullt | Positive | Pass |
AIP78_TC_015 | Verify user can create backfill with `run_backwards` as True | 1. Send a POST request to create a backfill job for a specific DAG using API with valid parameters. { |
| Positive | Pass |
| AIP78_TC_016 | Verify user cannot create backfill with reprocess behavior as None when there are already success DAG runs on same date |
|
| Negative | Pass |
AIP78_TC_017 | Verify user can create backfill with reprocess behavior as Completed. |
| Backfill should be created(internally we will clear the DAG run for same dates) | Positive | Pass |
AIP78_TC_018 | Verify user can create backfill with reprocess behavior as Failed. |
| Backfill should be created(internally we will clear the DAG run for same dates) | Positive | Pass |
AIP78_TC_019 | Verify user perform dry run using CLI |
| User should get list of dates for which backfill will be created | Positibe | Pass |