Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt

Use this file to discover all available pages before exploring further.

A dev fixture generator creates synthetic file names, file paths, MIME types, cron expressions, network-interface names and semantic-version values for tests. It helps developers and QA teams build repeatable sample records for parser tests, import jobs, scheduler flows and infrastructure screens without copying production settings.
Generate developer fixture data at spotzee.com/tools/dev-fixture-generator.

​
Why this matters

Small fixture sets age badly. A parser that only sees one file path, one MIME type or one cron expression can pass tests while still failing on real input shapes. Developer fixture data gives you varied values for upload handling, MIME routing, scheduler parsing, network-interface display and semantic-version comparison. And seeds make failures easier to reproduce because the same inputs can return the same output. Generated dev fixture data is test data only. It is not a verified infrastructure inventory, scheduler source of truth or production configuration. Each Extended API call deducts a small per-call amount from your Spotzee credit balance. See the Spotzee pricing page for live per-tool pricing.

​
How it works

1

Send the request

POST to /generic/data/generate/system with count. The count is a string from 1 to 100.
2

Choose a method

Use method=profile for expanded records, or choose one field method: commonFileExt, commonFileName, commonFileType, cron, directoryPath, fileExt, fileName, filePath, fileType, mimeType, networkInterface or semver.
3

Set method options

Send extension, mimeType, extension-count fields, interface fields, and cron flags when the selected method needs those controls.
4

Set repeatability

Send locale where supported and an optional numeric seed when the same dev fixture generator output needs to repeat in tests.
5

Read the response

The response returns data.systems[], generated, locale, optional seed, and the resolved method.

​
Method reference

MethodOutputMain parameters
profileExpanded system fixture recordcount, locale, seed, file, cron and network options
commonFileExtCommon file extensioncount, locale, seed
commonFileNameCommon file namecount, locale, seed, extension
commonFileTypeCommon file typecount, locale, seed
cronCron expressioncount, locale, seed, includeYear, includeNonStandard
directoryPathDirectory pathcount, locale, seed
fileExtFile extensioncount, locale, seed, mimeType
fileNameFile namecount, locale, seed, extension-count fields
filePathFile pathcount, locale, seed
fileTypeFile typecount, locale, seed
mimeTypeMIME typecount, locale, seed
networkInterfaceNetwork-interface namecount, locale, seed, interfaceType, interfaceSchema
semverSemantic versioncount, locale, seed
Use profile when you need many developer fixture fields together. Use a field method when your form, parser or import job only needs one value type.

​
What to watch for

  • Count outside 1 to 100. One request generates up to 100 system records. For more rows, call the endpoint again and vary the seed when you need a different batch.
  • Leading dot in extension. Send txt, not .txt, when commonFileName should use a specific extension.
  • Invalid MIME type input. Use type/subtype format such as application/json when fileExt should resolve from a MIME type.
  • Conflicting extension counts. Use either extensionCount or extensionCountMin / extensionCountMax. Do not send both shapes together.
  • Range values in the wrong order. extensionCountMin must be less than or equal to extensionCountMax.
  • Assuming production validity. Generated values are synthetic sample data. Do not treat them as real infrastructure records.

​
FAQs

A dev fixture generator can return systems[] records with method and value fields. Profile output can also include file extensions, file names, file paths, MIME types, cron expressions, network-interface names and semver values.
Yes. Set method=cron when a scheduler test needs cron expression values. The same method also works as a cron expression generator when display and parsing paths need coverage.
Yes. Use method=fileName for generated file-name values or method=commonFileName for common file names. Use it as a random file name generator with extension and extension-count fields when your test needs those shapes.
Yes. Set a numeric seed to reproduce output for the same count, locale, method and option values. Leave the seed blank when you want fresh random data generator output for exploratory QA.
No. It generates synthetic sample data for tests, seed scripts and demos. Do not treat returned paths, network-interface names or cron expressions as production configuration.
Read the dev fixture generator guide for endpoint options, response fields and integration patterns. The guide also shows where developer fixture data fits beside git, date, company and phone generators.

​
Try it

Generate developer fixture data in the browser at spotzee.com/tools/dev-fixture-generator, or call the Extended API when you need file, MIME, cron, network-interface and semver fixtures inside automated tests and seed scripts.