chore: test updates, ai guidance, and pr template#46
Conversation
Greptile SummaryThis PR adds
Confidence Score: 5/5Safe to merge — changes are additive (docs, parallelism) and the one code change is a straightforward correctness fix. All tests modified are stateless and use per-subtest fixtures, so the parallel annotations are safe. The No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[go test ./...] --> B[TestListPackages]
A --> C[TestMetadataForPackage]
A --> D[TestSecretNameForPackage]
A --> E[TestFormatPackageName]
A --> F[TestDisplayNameForApp]
A --> G[TestEndpointURL]
A --> H[TestToAPIApps]
A --> I[TestFilterByUserGroup]
A --> J[TestValidateJWT]
B --> B1[subtest t.Parallel]
C --> C1[subtest t.Parallel]
D --> D1[subtest t.Parallel]
E --> E1[subtest t.Parallel]
F --> F1[subtest t.Parallel]
G --> G1[subtest t.Parallel]
H --> H1[subtest t.Parallel]
I --> I1[subtest t.Parallel]
J --> J1[subtest t.Parallel]
Reviews (1): Last reviewed commit: "chore: applying best practice" | Re-trigger Greptile |
|
Left out uds-portal/src/pkg/config/config_test.go Line 34 in 8c723a2 Going to likely be pulling out the classification banner from those files (and the project) as it's now redundant with the UDS Core feature. When do that I can also address the variable for testing. |
Description
Related Issue
N/A, updating tests following suggestion from @daveworth
Type of change
Steps to Validate
Tests pass
Checklist before merging