Description
Sample integer serial dates around a caller boundary in the explicit 1900 or 1904 workbook system, retaining date-range and fictitious-day controls plus successful reverse conversions.
A parser corpus pairs literal input spellings or structured documents with observable parser results or explicitly constructed expectations. Successful parsing, semantic validity, and exact round-trip preservation are separate properties, so test records retain the relevant evidence.
Sample integer serial dates around a caller boundary in the explicit 1900 or 1904 workbook system, retaining date-range and fictitious-day controls plus successful reverse conversions.
When to use this tool
Use this generator to create reproducible spreadsheet serial date boundary corpus cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.
How to use the tool and how it works
- Supply system, startSerial, radius, count in the field shapes below. Set seed when you need an explicit replay.
- Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
- Read system, cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Draw integer serials from startSerial plus or minus radius in the selected 1900 or 1904 workbook system. Convert successful dates back to serials and retain date_range or fictitious_date controls as null date and reverse-conversion fields.1
Delegated operations used for this result: excel serial date to iso converter; iso date to excel serial export. Their calculation or parsing conventions apply to the corresponding result fields.2, 3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| system | System | Required. Text; one of "1900", "1904". |
| startSerial | Start Serial | Required. Safe integer. |
| radius | Radius | Required. Safe integer; minimum 0; maximum 8. |
| count | Requested count; the mechanics explain whether one draw expands into several returned records. | Required. Safe integer; minimum 1; maximum 16. |
| seed | Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed. | Optional. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| system | System | Required. Text; one of "1900", "1904". |
| cases | Cases | Required. Array of Object; no unknown keys.; minimum items 0; maximum items 16. |
| cases[].serial | Serial | Required. Safe integer. |
| cases[].isoDate | Iso Date | Required. Text; maximum UTF-16 length 64. or Null. |
| cases[].errorCode | Error Code | Required. Text; maximum UTF-16 length 64. or Null. |
| cases[].roundTripSerial | Round Trip Serial | Required. Safe integer. or Null. |
| randomness | Replay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional numeric replay seed; normalization and precedence are explained below. | Required. Safe integer. or Null. |
| randomness.source | Source | Required. Text; one of "context", "seed". |
An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.
{
"input": {
"system": "1900",
"startSerial": 60,
"radius": 1,
"count": 3,
"seed": 42
},
"output": {
"system": "1900",
"cases": [
{
"serial": 60,
"isoDate": null,
"errorCode": "fictitious_date",
"roundTripSerial": null
},
{
"serial": 60,
"isoDate": null,
"errorCode": "fictitious_date",
"roundTripSerial": null
},
{
"serial": 61,
"isoDate": "1900-03-01",
"errorCode": null,
"roundTripSerial": 61
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Negative serials are labeled date_range without passing the old converter's structural gate. The fictitious 1900 leap day is not a Gregorian date. Fractional times and spreadsheet timezone behavior are outside this corpus.
- A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
- The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.
Alternative or Complementary methods
For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.
References
Similar or alternative tools
- Random Numeric Parser Boundary Corpus Generator
Generate numeric spellings and malformed, overflow, and safe-integer controls with delegated number and integer parser outcomes.
- Random Spreadsheet Coordinate Navigation Quiz Generator
Generate bounded A1 coordinate and rectangular-range prompts with explicit absolute markers, then delegate one-based coordinate and row-major expansion answers.