Page History

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.
2. Modify DAG to Version 2.
3. Check UI representation for both versions.

UI displays correct DAG structure and code for each version with a version change indicator.

Functional

UI changes not implemented
Verified backend

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

Verified backend
GitHub Issue #44473

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

Verified backend

TC_AIP65_004

Ensure removed tasks are correctly shown in the grid view

1. Create a DAG with 3 tasks and run.
2. Modify DAG to remove a task and run again.
3. Check grid view for both DAG runs.

Removed tasks are shown without status boxes, and the toggle to exclude them works.

Functional

UI changes not implemented
Verified backend

TC_AIP65_003005

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.
2. Run tasks and observe the UI.

Version change indicator appears, and the tooltip reflects version change changes between task instances.

Functional

UI changes not implemented

TC_AIP65_004006

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.
2. Click on an older DAG run in the UI.

Rows animate to correct positions, and tasks are reordered accordingly.

Functional

UI changes not implemented

TC_AIP65_005007

Ensure disabled the clear button is disabled for removed tasks with proper explanation

1. Remove a task from the DAG.
2. Try to clear the removed task in the UI.

Clear The clear button is disabled with a tooltip explanation.

Functional

UI changes not implemented

TC_AIP65_006008

Validate DAG version tracking at TaskInstance try level

1. Run a task instance multiple times with DAG changes in between.
2. Navigate through task instance attempts.

Each attempt reflects the correct DAG version, with version history accessible.

Functional

TC_AIP65_007

Ensure correct representation for structural DAG changes mid-run

1. Create and run DAG Version 1.
2. Modify DAG structure and continue run.
3. Check graph view.

Separate graphs for each version are shown, with no merging. Toggle allows viewing each version individually.

Functional

Pass

TC_AIP65_008009

Test behavior when clearing an entire DAG run with older code

1. Clear all tasks in a completed DAG run.
2. Observe if the latest DAG version code is used.

Entire DAG run re-executes using the latest DAG version, with a clear indication in the UI.

Functional

TC_AIP65_009

Check clearing individual task instances from older DAG versions

1. Clear a task instance and inspect downstream behavior.

Task runs with the latest version code, and carets indicate version changes. Warning shown if downstream is not cleared.

Functional

GitHub Issue #44451
Verified backend behavior

TC_AIP65_010

Verify toggling between DAG code versions in code view

1. Run a DAG with multiple versions.
2. Switch between versions in the code view.

Code view updates to show the selected version accurately.

Functional

UI changes not implemented
Currently, code view is showing the latest for all runs.

TC_AIP65_011

Test task retries with DAG version change

1. Run a task that fails in DAG Version 1.
2. Modify DAG to Version 2 and retry.
3. Observe retry behavior in UI.

Task is retried with Version 2 DAG code, and the version change is indicated.

Functional

UI changes not implemented
Verified backend behavior

TC_AIP65_012

Check version history tracking details in task instance details

1. View task instance details in the UI.
2. Check if version history is properly details are displayed for each task.

Task instance details show the version history, including changes in DAG structure.

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.
2. Compare the UI outputs.

Each DAG run displays its corresponding version, with an indicator in the UI.

Functional

TC_AIP65_014

Ensure task instance retry behavior when a DAG version changes mid-run

1. Start a task in Version 1 and interrupt it.
2. Modify DAG to Version 2 and resume.

Task is retried using the new DAG version, and the UI reflects the version switch.

Functional

UI changes not implemented

TC_AIP65_015014

Verify the representation of failed tasks from older DAG versions

1. Run a task with Version 1 that fails.
2. Modify the DAG and run again.

Failed tasks from Version 1 remain represented as failed, with a version indicator.

Functional

UI changes not implemented

TC_AIP65_016015

Validate task dependencies after DAG version changes

1. Modify the DAG with added/deleted dependencies.
2. Run the updated DAG and check task dependencies.

Dependencies are updated in the UI according to the new DAG version, with proper visualization.

Functional

UI changes not implemented

TC_AIP65_017016

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

TC_AIP65_018

Verify version rollback behavior when a DAG run fails

1. Run a DAG Version 1 and cause failure.
2. Rollback to Version 0 and rerun.

Version rollback is reflected in the UI, and task executions follow the old version's logic.

FunctionalUI changes not implemented

TC_AIP65_019017

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

TC_AIP65_020018

Test version change behavior when a task is skipped due to dependencies

1. Modify a DAG to skip a task based on conditions.
2. Check the task's behavior across different versions.

Skipped tasks are shown with their respective version history in the UI.

Functional

Verified backend behavior

TC_AIP65_021019

Verify `dag_run`, `serialized_dag`, `task_instance`, and `dag_code` tables have Verify DAG table has a new field as dag`dag_version_idid`

1. Connect to DB the database.
2. Verify DAG table has the tables have a new field as dag`dag_version_idDAG table has id`.

The tables have a new field as dag`dag_version_idid`.

Database

Verified backend behavior

TC_AIP65_022020

Verify a new table `DagVersion` is created to track different DAG versions

1. Connect to DB & the database and check.

`DagVersion` table is created

Database

TC_AIP65_023

Verify database sanity

1. Update any DAG 2. Connect to Database and verify

SerializedDagModel, DagVersion, and DagCode should always have the same number of items at any time.

Database

TC_AIP65_024

Verify SerializedDagModel can be deleted without DagVersion and code deletion

1. Update any DAG 2. Use CLI, RESTAPI and UI to delete SerializedDagModel

There should not be a way through the CLI, RESTAPI and UI to delete SerializedDagModel without DagVersion and code deletion

Functional

Database

Verified backend behavior

TC_AIP65_025021

Execute Backfills for DAG

1. Execute Backfillsbackfills.

Latest The latest version should be used for backfills.

Functional

Verified backend behavior