-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Labels
kind/discussionTopical discussion; usually not changes to codebaseTopical discussion; usually not changes to codebaseneed/maintainers-inputNeeds input from the current maintainer(s)Needs input from the current maintainer(s)
Description
Overview
Some of our tests mention/link to a specification, e.g.
Spec: "https://specs.ipfs.tech/http-gateways/path-gateway/#content-disposition-response-header", |
Goal
We should make it easier for folks who are reading specs, to run conformance tests for that specific test, and potentialy even target specific sections of those specs.
Examples
Trying to test https://specs.ipfs.tech/http-gateways/trustless-gateway could be as easy as:
gateway-conformance test <...> --specs http-gateways/trustless-gateway
You could target a subsection of that test (i.e. https://specs.ipfs.tech/http-gateways/trustless-gateway/#dag-scope-request-query-parameter) with something like:
gateway-conformance test <...> --specs http-gateways/trustless-gateway/dag-scope-request-query-parameter
Concerns and other thoughts
Tight coupling these like this will cause some pain, but it will also keep our specifications and conformance tests accurate and up to date.
Related
Potentially related? #120
Similar to #86, but for keeping conformance tests closer to specifications.
Metadata
Metadata
Assignees
Labels
kind/discussionTopical discussion; usually not changes to codebaseTopical discussion; usually not changes to codebaseneed/maintainers-inputNeeds input from the current maintainer(s)Needs input from the current maintainer(s)