Skip to content

Conversation

@shashbha14
Copy link

Implements E2E tests for the Variables page as part of the UI E2E Test Scenarios meta issue.
This PR adds comprehensive end-to-end tests for the /variables page using Playwright, following the Page Object Model (POM) pattern established in PR #58548.

Changes Made

1. E2E Test Infrastructure

  • Playwright Configuration (playwright.config.ts) - Multi-browser test setup
  • Test Configuration (testConfig.ts) - Environment variables and settings
  • Git Ignore (.gitignore) - Exclude Playwright test artifacts

2. Page Object Models

  • BasePage - Common page interaction methods
  • LoginPage - Authentication handling
  • VariablesPage - Comprehensive Variables page interactions with 20+ methods

3. Test Specifications

  • variables.spec.ts - 15 comprehensive test cases
  • Complete test coverage for all Variables page features
  • Automated test data creation and cleanup

4. Documentation

  • README.md - Complete guide for running and writing E2E tests
  • Includes setup instructions, troubleshooting, and examples

Test Coverage

✅ Variables list display
✅ Create variable (encrypted and non-encrypted)
✅ Edit variable
✅ Delete variable (single and bulk)
✅ Search variables (exact and wildcard patterns)
✅ Import variables from JSON file
✅ Pagination navigation
✅ Column sorting (key, value, description)

Testing Approach

  • Framework: Playwright v1.48.2
  • Pattern: Page Object Model (POM)
  • Browsers: Chromium, Firefox, WebKit
  • Test Data: Auto-generated with timestamps, cleaned up in afterAll
  • No hardcoded values: Uses testConfig and dynamic data

How to Run

cd airflow/ui
pnpm install
pnpm exec playwright install
pnpm test:e2e

- Implement Playwright E2E test framework
- Add Page Object Models (BasePage, LoginPage, VariablesPage)
- Add 15 comprehensive test cases for Variables page
- Tests cover CRUD, search, pagination, sorting, and import
- Follow POM pattern and work across Chromium, Firefox, WebKit
@shahar1
Copy link
Contributor

shahar1 commented Jan 16, 2026

Please resolve conflicts.
CC: @vatsrahul1001

@shashbha14
Copy link
Author

Thank you for the review! The repository structure has changed since I created this branch. To avoid complex merge conflicts, I'll close this PR and create a new one based on the latest main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants