Aias00 opened a new issue, #6588:
URL: https://github.com/apache/shenyu/issues/6588

   ## Description
   `find shenyu-admin/src/test -name "<Name>ControllerTest.java"` confirms no 
test exists for `NamespaceController`, `AiProxyApiKeyController`, 
`DiscoveryController`, `DiscoveryUpstreamController`, 
`ProxySelectorController`. NamespaceController is the multi-tenancy boundary 
(create/delete namespaces — issues #5945, #6481, #6482 already surfaced bugs 
here). AiProxyApiKeyController handles AI-proxy api-key material (secrets). 
DiscoveryController/DiscoveryUpstreamController manage upstream instance config 
(the surface of bugs #6479, #6517, #6466). ProxySelectorController owns gateway 
routing config (#6045, #6480). Contrast: AppAuthController, 
ConfigsExportImportController, PermissionController, DataPermissionController, 
ResourceController, RoleController, DashboardUserController, SandboxController, 
ShenyuClientHttpRegistryController all DO have tests.
   
   ## Location
   ```
   shenyu-admin/.../controller/NamespaceController.java
   AiProxyApiKeyController.java
   DiscoveryController.java
   DiscoveryUpstreamController.java
   ProxySelectorController.java
   ```
   
   ## Impact
   RBAC/namespace/secret surfaces regress silently. These are exactly the 
controllers that produced the recent cluster of open NPE/corruption bugs.
   
   ## Suggested fix
   Add `@WebMvcTest` controller tests (mirror the existing 
`AppAuthControllerTest`/`ConfigsExportImportControllerTest` style) for each, 
with service mocks covering happy + error + permission-denied paths.
   
   ## Related existing issue(s)
   None
   
   _Identified during the 2026-08-02 audit; full list in 
[`docs/issue-candidates-2026-08-02.md`](docs/issue-candidates-2026-08-02.md)._


-- 
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]

Reply via email to