Skip to content

Comments

chore: e2e for secrets management ui#1830

Open
maxy-shpfy wants to merge 1 commit intomasterfrom
02-19-chore_e2e_for_secrets_management_ui
Open

chore: e2e for secrets management ui#1830
maxy-shpfy wants to merge 1 commit intomasterfrom
02-19-chore_e2e_for_secrets_management_ui

Conversation

@maxy-shpfy
Copy link
Collaborator

@maxy-shpfy maxy-shpfy commented Feb 20, 2026

Description

Added comprehensive test identifiers (data-testid attributes) to all secrets management components and implemented a complete end-to-end test suite. The test identifiers enable reliable automated testing of the secrets management functionality, covering all user interactions including creating, editing, removing secrets, and handling empty states.

Related Issue and Pull requests

Type of Change

  • Bug fix
  • New feature
  • Improvement
  • Cleanup/Refactor
  • Breaking change
  • Documentation update

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Secrets UI e2e.mov (uploaded via Graphite)

Test Instructions

  1. Enable the secrets beta flag in personal preferences
  2. Click the "Manage Secrets" button to open the dialog
  3. Verify all interactive elements have proper test identifiers
  4. Run the new e2e test suite: npm run test:e2e -- secrets-management.spec.ts
  5. Test covers: opening dialog, adding secrets, editing secrets, removing secrets, canceling operations, and empty state handling

Additional Comments

The e2e tests run in serial mode due to shared secrets state and are designed to be idempotent with proper cleanup. Each test creates and removes its own test data to avoid interference between test runs.

This test spec fully interacts with a backend.

Copy link
Collaborator Author

maxy-shpfy commented Feb 20, 2026

@maxy-shpfy maxy-shpfy changed the base branch from 02-19-fix_e2e_tests_failures to graphite-base/1830 February 20, 2026 16:09
@maxy-shpfy maxy-shpfy force-pushed the 02-19-chore_e2e_for_secrets_management_ui branch from d15fb13 to 2d853a5 Compare February 20, 2026 16:10
@graphite-app graphite-app bot changed the base branch from graphite-base/1830 to master February 20, 2026 16:10
@maxy-shpfy maxy-shpfy force-pushed the 02-19-chore_e2e_for_secrets_management_ui branch 2 times, most recently from 12e92e9 to 3df6bd9 Compare February 20, 2026 17:35
@maxy-shpfy maxy-shpfy force-pushed the 02-19-chore_e2e_for_secrets_management_ui branch from 3df6bd9 to 59e1f5d Compare February 20, 2026 23:50
@maxy-shpfy maxy-shpfy marked this pull request as ready for review February 20, 2026 23:55
@maxy-shpfy maxy-shpfy requested review from a team as code owners February 20, 2026 23:55
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.

1 participant