Repository navigation
Add comprehensive Postman tests for search - #135
Merged
Merged
Conversation
jdaigneau5
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
POST /searchfield, representative filter combinations, deterministic validation failures, and optional manual fault-injection checks.status: "ok"consistently from successful semantic post-filter searches so CVSS, SSVC, KEV date,cpeName, andvirtualMatchStringresponses match the standard search response shape.Why These Changes Are Needed
Semantic post-filter searches returned pagination and hit data but omitted the top-level success status produced by ordinary searches. This caused response-contract checks to fail even when the requested filter returned the correct CVE records.
The API also lacked a maintainable manual test collection covering its complete search contract. The builder now checks that every documented
SearchRequestproperty has positive Postman coverage and generates portable local/dev artifacts from one source file.Primary Files
controllers/searchController.js: adds the missing success status to optimized post-filter responses.controllers/searchController.test.js: locks the consistent response shape across semantic filter paths.test/postman/buildCollection.js: defines and generates the complete manual contract suite.test/postman/CVE-Search-API.postman_collection.json: importable generated collection.test/postman/local.postman_environment.json: localhost configuration.test/postman/dev.postman_environment.json: deployed dev configuration.test/postman/README.md: usage, fixture, maintenance, and fault-injection guidance.README.md: links to the Postman documentation.