Nobody reads */15 9-17 * * 1-5 correctly at a glance. Every expression here comes with a description, so you can generate a set of schedules and check that your parser agrees with what the words say.
What you can control
- Three flavours: Unix five-field, Quartz with a seconds field, and the AWS EventBridge
cron(...)wrapper. - Plain-English descriptions for every expression, generated from the fields rather than looked up.
- Presets for the common shapes — sub-hourly, daily, weekly, monthly — plus a fully random mode.
- Random mode produces ranges, steps and lists, which is where most cron parsers stop being correct.
Testing ideas
- Flavours. Unix cron has five fields, Quartz six (with seconds), AWS EventBridge its own syntax. Generate each to test the parser you actually use.
- Next run. Show the next run time and compare it with your scheduler's own calculation.
- Descriptions. Use the plain-English column to test a schedule picker's human-readable summary.
- Edge schedules. Edit a generated monthly expression to run on day 31, or at 00:30 in a zone with daylight saving, to find short-month and time-zone bugs.
What this is not
Quartz and AWS both use six fields but place them differently, and AWS uses a year field where Quartz uses seconds. Check which one your scheduler expects before pasting.