test: Add Unit Test Coverage for Query Util

[kartikangiras]

Description

Add unit test coverage for pkg/utils/query.go

• relates to [feature]: Add Unit Test coverage for Utils #1025

Type of Change

Please select the relevant type.

• Bug fix
• New feature
• Refactor
• Documentation update
• Chore / maintenance

Changes

• pkg/utils/query_test.go: 15 tests for BuildQueryParam, input validation, key validation

[kartikangiras]

@NucleoFusion Could you PTAL into this PR.

[Copilot]

Pull request overview

Adds unit tests to cover the query-string builder utility used for list command filtering, improving confidence in CLI query construction and validation behavior.

Changes:

• Introduces unit tests for utils.BuildQueryParam covering empty input, fuzzy/exact/range query generation, and combined modes.
• Adds negative tests for invalid argument formats and invalid keys.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kartikangiras]

Hey @qcserestipy , I have made changes and resolved the review remarks. Could you PTAL.

[qcserestipy]

Nice coverage of the happy paths and the format/key validation errors. A few edge cases in BuildQueryParam aren't exercised yet, and they're the interesting ones because they reveal some fuzzy parsing behavior worth pinning down:

1. Values containing = — strings.Split(v, "=") returns 3 parts for name=foo=bar, so it's rejected as an "invalid arg" even though the intent is a value with an = in it. Using strings.SplitN(v, "=", 2) would fix this. Either way, a test should document the chosen behavior.

2. Empty value — name= passes the len(kv) != 2 check and produces name=~ (fuzzy) / name= (match). Likely unintended; currently untested.

3. Empty range bounds — size=1~ or size=~100 both pass and emit size=[1~] / size=[~100]. Worth a test to confirm whether that's acceptable or should error.

Optional: these 15 functions are nearly identical in shape — folding them into a single table-driven test with t.Run subtests (as done elsewhere in the repo) would make adding the above cases a one-line change each.

Also, since #1025 asks for both query.go and reflect.go coverage and this PR is query-only, consider dropping "Fixes #1025" here (or marking it partial) so the issue isn't auto-closed before the reflect tests land.

[qcserestipy]

As mentioned

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.