Frontend testing strategy

Write tests for Grafana frontend code that pass review on the first pass. Goals: assert concrete behavior, not existence; keep test descriptions honest; verify the test actually exercises the target code path; and stabilize the known flake classes. Several codeowner paths are opted into the gating check-frontend-test-coverage.yml check, so coverage that drops fails CI.

Resolve the target

Interpret the argument to decide scope:

• A file path → test that file (create or extend its co-located *.test.ts(x)).
• A directory / component / module name → the source files under it lacking meaningful coverage.
• "current file" / no path but a file is open → the open file.
• No argument → ask which file/area; don't blanket-generate.