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* |
|---|---|---|---|---|
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 |
TC_AIP65_002 | 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 toggle to exclude them works. | Functional |
TC_AIP65_003 | Verify that non-structural DAG code changes are reflected properly in UI | 1. Modify a DAG without changing task structure. | Version change indicator appears, and tooltip reflects version change between task instances. | Functional |
TC_AIP65_004 | Check UI for task reordering animation when an older DAG version is selected | 1. Run DAG in Version 1 and then modify to Version 2. | Rows animate to correct positions, and tasks are reordered accordingly. | Functional |
TC_AIP65_005 | Ensure disabled clear button for removed tasks with proper explanation | 1. Remove a task from DAG. | Clear button is disabled with a tooltip explanation. | Functional |
TC_AIP65_006 | Validate DAG version tracking at TaskInstance try level | 1. Run a task instance multiple times with DAG changes in between. | Each attempt reflects 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. | Separate graphs for each version are shown, with no merging. Toggle allows viewing each version individually. | Functional |
TC_AIP65_008 | 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 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 |
TC_AIP65_010 | Verify toggling between DAG code versions in code view | 1. Run DAG with multiple versions. | Code view updates to show the selected version accurately. | Functional |
TC_AIP65_011 | Test task retries with DAG version change | 1. Run a task that fails in DAG Version 1. | Task is retried with Version 2 DAG code, and version change is indicated. | Functional |
TC_AIP65_012 | Check version history tracking in task instance details | 1. View task instance details in the UI. | Task instance details show the version history, including changes in DAG structure. | Functional |
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 |
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. | Task is retried using the new DAG version, and the UI reflects the version switch. | Functional |
TC_AIP65_015 | 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 |
TC_AIP65_016 | Validate task dependencies after DAG version changes | 1. Modify DAG with added/deleted dependencies. | Dependencies are updated in the UI according to the new DAG version, with proper visualization. | Functional |
TC_AIP65_017 | Test UI behavior when changing DAG versions after task completion | 1. Complete a task in Version 1. | 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. | Version rollback is reflected in the UI, and task executions follow the old version's logic. | Functional |
TC_AIP65_019 | Ensure the correct representation of DAG versions during parallel task execution | 1. Run parallel tasks with different versions of a DAG. | Tasks executed in different versions appear correctly separated and aligned in the UI. | Functional |
TC_AIP65_020 | 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 |
TC_AIP65_021 | Verify DAG table has a new field as dag_version_id | 1. Connect to DB | DAG table has a new field as dag_version_id | Database |
TC_AIP65_022 | Verify a new table `DagVersion` is created to track different DAG versions | 1. Connect to DB & 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 |
TC_AIP65_025 | Execute Backfills for DAG | 1. Execute Backfills | Latest version should be used for backfills | Functional |