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* |
|---|---|---|---|---|---|
TC_AIP65_001 | Verify DAG version displayed correctly in UI when DAG structure changes between two DAG runs | 1. Create and run DAG Version 1. |
UI |
displays correct DAG structure and code for each version with a version change indicator. | Functional |
Verified backend
Pass | ||||
TC_AIP65_002 | Verify a new DAG version is created on updating any DAG params | 1. Try Updating DAG params | A new DAG version should be created in the `DAG_version` table. | Functional |
GitHub Issue #44473
Pass | ||||
TC_AIP65_003 | Verify changing task implementation does not create a new DAG version | 1. Try to change any task implementation. | Changing task implementation should not create a new DAG Version. | Functional |
Pass | ||||
TC_AIP65_004 | Ensure removed tasks are correctly shown in the grid view | 1. Create a DAG with 3 tasks and run. | Removed tasks are shown without status boxes, and the toggle to exclude them works. | Functional |
FAIL https://github.com/apache/airflow/issues/47857 | ||||
TC_AIP65_005 | Verify that non-structural (e.g., task rename) DAG code changes are reflected properly in the UI | 1. Modify a DAG without changing task structure. | Version change indicator appears, and the tooltip reflects version changes between task instances. | Functional |
TC_AIP65_006 | Check UI for task reordering animation when an older DAG version is selected | 1. Run DAG in Version 1 and then modify it to Version 2. | Rows animate to correct positions, and tasks are reordered accordingly. | Functional | UI changes not implemented |
TC_AIP65_007 | Ensure the clear button is disabled for removed tasks with proper explanation | 1. Remove a task from the DAG. | The clear button is disabled with a tooltip explanation. | Functional |
Blocked by TC_AIP65_004 | |||||
TC_AIP65_008 | Validate DAG version tracking at TaskInstance try level | 1. Run a task instance multiple times with DAG changes in between. | Each attempt reflects the correct DAG version, with version history accessible. | Functional | Pass |
TC_AIP65_009 | Test behavior when clearing an entire DAG run with older code | 1. Clear all tasks in a completed DAG run. | Entire DAG run re-executes using the latest DAG version, with a clear indication in the UI. | Functional |
GitHub Issue #44451
Verified backend behavior
Pass | ||||
TC_AIP65_010 | Verify toggling between DAG code versions in code view | 1. Run a DAG with multiple versions. | Code view updates to show the selected version accurately. | Functional |
UI changes not implemented
Currently, code view is showing the latest for all runs.
Pass | ||
TC_AIP65_011 | Test task retries with DAG version change | 1. Run a task that fails in DAG |
Version | Task is retried with Version 2 DAG code, and the version change is indicated. | Functional |
UI changes not implemented
Verified backend behavior
Pass | |||||
TC_AIP65_012 | Check version details in task instance details | 1. View task instance details in the UI. | Task instance details show the version. | Functional | Pass |
TC_AIP65_013 | Validate UI display when selecting DAG runs from different versions | 1. Select different DAG runs from older and newer versions. | Each DAG run displays its corresponding version, with an indicator in the UI. | Functional | UI changes not implemented |
TC_AIP65_014 | Verify the representation of failed tasks from older DAG versions | 1. Run a task with Version 1 that fails. | Failed tasks from Version 1 remain represented as failed, with a version indicator. | Functional | UI changes not implemented |
TC_AIP65_015 | Validate task dependencies after DAG version changes | 1. Modify the DAG with added/deleted dependencies. | Dependencies are updated in the UI according to the |
TC_AIP65_016
Test UI behavior when changing DAG versions after task completion
1. Complete a task in Version 1.
2. Change the DAG version and observe UI changes.
UI updates to show task completion with the appropriate version.
Functional
UI changes not implemented
TC_AIP65_017
Ensure the correct representation of DAG versions during parallel task execution
1. Run parallel tasks with different versions of a DAG.
2. Compare the UI for each task.
Tasks executed in different versions appear correctly separated and aligned in the UI.
Functional
Exiting DAG RUN updates with the new DAG version in the DAG run and task instance table
UI changes not implemented
Latest DAG version, with proper visualization. | Functional |
UI changes not implemented
Pass |
TC_AIP65_018 | Test version change behavior when a task is skipped due to dependencies | 1. Modify a DAG to skip a task based on conditions. | Skipped tasks are shown with their respective version history in the UI. | Functional |
Pass | |
TC_AIP65_019 | Verify |
`serialized_dag`, `task_instance`, and `dag_code` tables have a new field as `dag_version_id` | 1. Connect to the database. | The tables have a new field as `dag_version_id`. | Database |
Pass | ||||
TC_AIP65_020 | Verify a new table `DagVersion` is created to track different DAG versions | 1. Connect to the database and check. | `DagVersion` table is created. | Database |
Pass | ||||
TC_AIP65_021 | Execute Backfills for DAG | 1. Execute backfills. | The latest version should be used for backfills. | Functional |
Pass |