How is this different from the boundary value generator?

This asks a scenario question about behaviour — what happens if a request arrives twice, or a list is empty. The boundary value generator hands you a specific value to test with, like an empty string or a maximum integer. Use this to decide what to test, and that one for a concrete value to test it with.

Edge Case Prompt Generator

Suggests a 'what happens if…' testing question — an empty list, a dropped connection, a boundary date — to jog which edge case to check next when test coverage starts to feel thin.

How many

Don't repeat what I've already seen

Your result will appear here.

What you'll get

This generator draws from a hand-checked list of 20 entries. Here is a spread of 6 of them, so you can see the style before you generate:

What happens if the input field is left completely empty?
What happens if a list has exactly one item?
What happens with a value at the exact maximum allowed length?
What happens if the date field receives a future date?
What happens if the user's session expires mid-action?
What happens if a paginated request asks for a page beyond the last one?

A fixed sample of the list, not a live draw — your own results are picked at random from all 20, without repeating until the list runs out. Original authoring for Generate Random — general software-testing heuristics.. Last reviewed 2026-07-18.

How to use this tool

Press generate for a prompt.
Check it against your feature, or generate again.

Common use cases

Filling gaps in test coverage
QA testing-session warm-up
Code review discussion prompts

Limitations and good to know

20 fixed, general-purpose prompts. They are starting points for thinking about edge cases, not a complete or codebase-specific test plan.
A prompt only asks the question; it does not know your feature's actual behaviour, so some prompts will not apply and some real edge cases specific to your domain will not appear here at all.
Nothing is tracked between visits, so there is no record of which prompts you have already worked through.

Practical tips

Work through the generated cases against an existing feature rather than a new one; edge cases are usually found in code that already looks finished.
Write a test for any case that surprises you, whether or not it currently fails.

Entries are chosen with your browser's cryptographic random number generator, so every entry on the list is equally likely. How Generate Random works.

Frequently asked questions

How is this different from the boundary value generator?: This asks a scenario question about behaviour — what happens if a request arrives twice, or a list is empty. The boundary value generator hands you a specific value to test with, like an empty string or a maximum integer. Use this to decide what to test, and that one for a concrete value to test it with.