Spec Compliance Test App #64
Labels
dif/easy
Someone with a little familiarity can pick up
effort/days
Estimated to take multiple days, but less than a week
help wanted
Seeking public contribution on this issue
kind/support
This is a question or a request for support
need/community-input
Needs input from the wider community
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
topic/devexp
Developer experience related things
topic/docs
Improvements or additions to documentation
Summary
<access-token>
and the URL with API<endpoint>
and runs a set of testsI'm available to review / feed edge cases is anyone wants to pick this up.
Implementation details
Create JS client library
@ipfs-shipyard/pinning-service-client
or similarCLI Compliance Test suite
The compliance test would be a separate package (
@ipfs-shipyard/pinning-service-complicance-checks
) that uses the client library to run tests and exits with code 0 if there were no hard errors:Web interface (nice to have)
Would be nice to have a static website with two inputs for
<access-token>
and<endpoint>
and "Test" button, but this is lower priority than CLI tool (we want something that can run automatically on CI to constantly validate services we list in ipfs-webui – ipfs/ipfs-webui#1854 (comment))Test scenarios
Below are things we want to test, in order:
MVP list
GET /pins
) in all states ipfs-shipyard/pinning-service-compliance#4pin
ipfs-shipyard/pinning-service-compliance#5DELETE /pins/{requestid}
ipfs-shipyard/pinning-service-compliance#7match
ipfs-shipyard/pinning-service-compliance#9The text was updated successfully, but these errors were encountered: