DSingh0304 opened a new issue, #3306: URL: https://github.com/apache/apisix-dashboard/issues/3306
## Please describe your feature The current E2E test suite tests Consumer CRUD and credential management in isolation ([consumers.crud-all-fields.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/consumers.crud-all-fields.spec.ts:0:0-0:0), [consumers.credentials.list.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/consumers.credentials.list.spec.ts:0:0-0:0)), but there is no test that exercises the complete authentication workflow end-to-end through the UI: 1. Create a Route protected by an auth plugin (e.g. `key-auth`) 2. Create a Consumer with a matching credential 3. Verify both resources are correctly configured and linked in the UI This is the most common real-world APISIX workflow for API authentication and is currently untested at the integration level. ## Describe the solution you'd like Add a new file `e2e/tests/hot-path.consumer-auth-route.spec.ts` following the same pattern as the existing [hot-path.upstream-service-route.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/hot-path.upstream-service-route.spec.ts:0:0-0:0). The test would: 1. Create a Route with URI `/anything`, method `GET`, and the `key-auth` plugin attached 2. Create a Consumer with a `key-auth` credential 3. Verify both resources are correctly saved and visible in the UI 4. Clean up via `deleteAllRoutes` / `deleteAllConsumers` in `afterAll` ## Describe alternatives you've considered The isolated tests ([consumers.crud-all-fields.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/consumers.crud-all-fields.spec.ts:0:0-0:0) and [consumers.credentials.list.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/consumers.credentials.list.spec.ts:0:0-0:0)) already cover Consumer and credential CRUD individually. However, they do not test the composition of a Consumer credential with a protected Route, which is a distinct and critical user workflow. ## Additional context - Existing hot-path test for reference: [e2e/tests/hot-path.upstream-service-route.spec.ts](cci:7://file:///home/deep/Desktop/Code/Organizations/apisix-dashboard/e2e/tests/hot-path.upstream-service-route.spec.ts:0:0-0:0) - Related: #3073 I'd like to work on this if the approach looks good. Happy to adjust the scope based on your feedback before opening a PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
