ipfs/kubo

need api tests

Open

#4017 opened on Jun 28, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/test

Description

We should add tests that verify the api output of each endpoint. We recently broke the output of ipfs repo gc without noticing until @ligi pointed it out.

Contributor guide

Tech stack
gorest api
Domain
testingbackendapi
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingAPI testingIPFS concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the current API endpoints in the kubo codebase, particularly the `ipfs repo gc` command. Look at existing test files for patterns. Identify all endpoints that need test coverage. Consider using Go's testing framework to write HTTP tests against the API server.