Test Case ID

Test Scenario

Test Steps

Expected Result

*TC_AIP79_001*

Verify Flask AppBuilder is no longer required to run the webserver and UI

1. Remove FAB Provider from the environment.
2. Start the Airflow webserver.

The Airflow webserver starts successfully without FAB installed or configured.

*TC_AIP79_002*

FAB auth manager functionality through provider

1. Install the FAB provider.
2. Configure the FAB auth manager.
3. Verify login and authorization features.

The FAB auth manager functions as expected when installed via the FAB provider, including login and authorization.

*TC_AIP79_003*

Deprecation of appbuilder_menu_items

1. Install a plugin using appbuilder_menu_items.
2. Start the webserver.
3. Access the menu items in the UI.

The menu items are displayed in the UI, and a warning is logged indicating deprecation of appbuilder_menu_items.

*TC_AIP79_004*

Verify user can create a new menu item

1. Try creating a new menu item using FASTAPI

User should be able to create a new menu item

*TC_AIP79_005*

Core Airflow runs with minimal auth backend

1. Configure the minimal auth backend in Airflow core.
2. Start the webserver.

The webserver runs successfully with the minimal auth backend, allowing unrestricted actions in local environments.

*TC_AIP79_006*

Backwards compatibility for FAB plugins

1. Install a plugin that uses appbuilder_views.
2. Start the webserver.
3. Access the plugin views.

The plugin views using appbuilder_views work as expected without requiring modifications.

*TC_AIP79_007*

FAB DB commands in the provider

1. Install the FAB provider.
2. Run the FAB-specific DB commands (migrate/reset/etc.).

The FAB provider manages its DB tables independently, and all DB commands work without errors.

*TC_AIP79_008*

Smooth upgrade path from Airflow 2 to 3

1. Upgrade an Airflow 2 instance using FAB auth and plugins to Airflow 3.
2. Start the webserver.

The instance upgrades successfully, and existing FAB auth and plugin functionalities continue to work as expected.

*TC_AIP79_009*

Backwards compatibility for flask_blueprints

1. Install a plugin that uses flask_blueprints.
2. Start the webserver.
3. Access the plugin views.

The plugin views using flask_blueprints work as expected without requiring modifications.

  • No labels