The cases are directly copied (or lightly adapted) from rpmmd_mock/fixtures. The purpose of the mocks/dnfjson package is to create files with data for testing the dnfjson package without the need to call the dnf-json script. Each public function creates a file with test responses in the same format as the dnf-json script's responses (either valid results or errors). The dnfjson.Solver can be configured to call the new ./cmd/mock-dnf-json program with the test data file as an argument and a valid dnf-json request for input. The mock-dnf-json checks the input request for unknown fields before responding with the contents of the file. Each test case file contains two responses, one for each command supported by dnf-json: "depsolve" and "dump". mock-dnf-json responds with the appropriate data based on the command in the request. This is necessary for tests that require both commands in the same call, e.g., tests of the weldr API's moduleInfoHandler() which fetches a package list and then needs to depsolve a subset of those packages. There are also cases when we want one of the two responses to be an error. The mock-dnf-json program will return with an error code if it can successfully unmarshal the intended response into the dnfjson.Error type. |
||
|---|---|---|
| .. | ||
| dnfjson.go | ||