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_001 | Verify successful renaming of Datasets to Assets in the Airflow UI. | 1. Open the Airflow UI. 2. Navigate to the Datasets view. 3. Check if the term "Datasets" has been replaced by "Assets." | The term "Datasets" should be replaced with "Assets" in the UI, including the view name and any dataset references. | Positive | Pass |
TC_002 | Verify that the Asset class can be instantiated with a valid name. | 1. Create a new asset using `Asset(name="test_asset")`. 2. Check if the asset is successfully instantiated. | The asset should be instantiated with the provided name without errors. | Positive | Pass |
TC_003 | Verify that an Asset must have either a name or uri. | 1. Create an asset without providing either name or uri. 2. Observe the behavior. | The system should raise an error indicating that at least one of name or uri is required. | Negative | Pass |
TC_004 | Verify grouping of assets by the group attribute in the UI. | 1. Create assets with different group values (e.g., model and dataset). 2. Open the Assets view in the UI. 3. Check if the assets are correctly grouped by their group attribute. | Assets should be displayed under their respective groups in the Assets view (e.g., model, dataset). | Positive | Implementation pending |
TC_005 | Verify creation of asset subclasses like Dataset and Model. | 1. Instantiate a Dataset and a Model subclass. 2. Check if the objects are created successfully. | Both the Dataset and Model subclasses should be instantiated without errors. | Positive | Pass |
TC_006 | Verify that subclassed assets (like Dataset) are auto-grouped by their types in the UI. | 1. Create assets using Dataset and Model. 2. View them in the Assets view in the UI. 3. Check if they are grouped under their respective types (dataset, model). | Assets should be auto-grouped by their type (e.g., dataset, model) in the UI. | Positive | Implementation pending |
TC_007 | Test for error when attempting to create assets with duplicate name. | 1. Create two assets with the same name value. 2. Check for errors or warnings. | The system should raise an error indicating a duplicate asset name. | Negative | Pass |
TC_008 | Validate the display of Asset objects in the Airflow web UI after creation. | 1. Create several assets. 2. Run a DAG utilizing these assets. 3. Open the UI and check if the assets are listed correctly under the Assets view. | All created assets should appear in the Assets view, reflecting correct data. | Positive | Pass |
TC_009 | Verify proper URI format handling in Asset instantiation. | 1. Create an asset using an `ObjectStoragePath` as the `uri` argument. 2. Check if it is converted to a URI string. | The `ObjectStoragePath` should be correctly converted to a URI string during asset instantiation. | Positive | Pass |
TC_010 | Validate that the task’s inlets and outlets are correctly tied to the associated assets. | 1. Create a DAG with tasks using inlets and outlets pointing to assets. 2. Run the DAG and check task execution results. | The tasks should execute correctly, using the inlets and outlets to interact with the assets. | Positive | Pass |
TC_011 | Verify color coding for different asset groups in the UI. | 1. Create assets belonging to different groups (e.g., dataset, model). 2. Check if the assets are color-coded according to their group in the UI. | The assets should be color-coded by their group in the Assets view. | Positive | Not implemented |
TC_012 | Verify that assets are updated periodically in Airflow as expected. | 1. Create a periodic DAG that updates assets. 2. Run the DAG multiple times. 3. Check if the assets are updated incrementally or replaced based on configuration. | The assets should either be replaced, appended to, or versioned as expected after each DAG run. | Positive | Pass |
TC_013 | Validate asset updates when used in backfill operations. | 1. Create assets and backfill them in a DAG run. 2. Check if assets are updated retroactively as expected. | Assets should update correctly based on the backfill operation. | Positive | Pass |
TC_014 | Test asset categorization with user-defined subclasses. | 1. Create a custom subclass of Asset. 2. Instantiate the subclass and check if it appears in the Assets view. | The custom asset should appear in the Assets view, categorized according to its type or group. | Positive | Pass |
TC_015 | Validate an asset is represented on web UI by name when asset is created by both arguments name and uri. | 1. Create an asset by providing both `name` and `uri`. 2. Observe the behavior. | The asset should be represented on web UI by `name` attribute value. | Positive | Pass |
TC_016 | Validate asset APIs have an attribute `name` in addition to `uri`. | 1. Create an asset by providing `name` attribute only. 2. Run list assets API. 3. Observe the API response. | The API response should have `name` attribute with the correct value. | Positive | Pass |
TC_017 | Validate asset events are created for Asset subclasses. | 1. Create an asset using Dataset/Model class. 2. Trigger the DAG which utilizes the above asset as an outlet. | Verify an asset event is created on the Assets page. | Positive | Pass |
TC_018 | Validate the updation of asset group. | 1. Create an asset which belongs to the asset group. 2. Once Airflow is up and running, update the asset group to dataset. | Asset group should get updated. | Positive | Pass |