GraphQL Error Response (JSON)
GraphQL error response with message and location — negative case for GraphQL clients.
{
"errors": [
{
"message": "Cannot query field 'foo' on type 'User'.",
"locations": [
{
"line": 2,
"column": 3
}
]
}
]
}
Specifications
- Kind
- GraphQL error
- Errors
- 1
Testing contract
Expected to pass- Scenario
- Exercise GraphQL Error Response (JSON) in its api workflow. GraphQL error response with message and location — negative case for GraphQL clients.
- Expected result
- top-level keys are errors; array lengths: errors=1. Declared feature checks: kind=GraphQL error; errors=1.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“GraphQL Error Response (JSON)” is a deterministic Novus Examples fixture for API testing, JSON parsing, Error handling. OpenAPI/Swagger specs, GraphQL SDL, JSON Schema, paginated and problem+json error payloads, and webhook samples, for testing API clients, mock servers, contract tests, and schema validators.
Documented properties for this file: JSON · 200 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("graphql-error-response.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonDependency Alerts Feed (JSON)The shape a hosted dependency-alert API returns: alerts with lifecycle state, a nested advisory, a patched-version pointer and an explicitly null dismissed_reason on the alerts that were not dismissed. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
- jsonApi Batch ResponseBatch API response mixing success and failure per sub-request.
- jsonAPI Cursor Pagination — Page 1 (JSON)Cursor-paginated SAMPLE API response page 1 with nextCursor metadata.
- jsonAPI Cursor Pagination — Page 2 (JSON)Cursor-paginated SAMPLE API response page 2 with nextCursor metadata.
- jsonApi Empty Page ResponseEmpty paginated response — edge case for UI empty states and merge logic.
- jsonApi Link Header PaginationRFC 5988 Link header pagination metadata as JSON for HTTP client tests.
Generated by generation/data_wave_f.py. Free for any use, no attribution required, license.