Test data

Test data plays a critical role in how effectively software is validated. Different input types behave differently across APIs, user interfaces, and integrations. This page brings together practical test data references for common input types such as booleans, dates, names, and URLs.

Use these examples to design realistic test scenarios, uncover edge cases, and improve overall test coverage.

- Boolean data
- Numeric data

Boolean test data

Boolean inputs look simple, but real systems accept far more than true and false. APIs, UI forms, CSV uploads, and integrations interpret Boolean values differently. This page provides a practical reference of valid, boundary, empty, and invalid Boolean test data. Use these examples to design stronger test scenarios and avoid silent logic failures.

Valid boolean test data

#	Valid Value	#	Valid Value
1	true	16	"NO"
2	false	17	"on"
3	TRUE	18	"off"
4	FALSE	19	"ON"
5	"true"	20	"OFF"
6	"false"	21	True
7	"TRUE"	22	False
8	"FALSE"	23	"True"
9	1	24	"False"
10	0	25	"enabled"
11	"1"	26	"disabled"
12	"0"	27	"Y"
13	"yes"	28	"N"
14	"no"	29	Boolean(true)
15	"YES"	30	Boolean(false)

Boundary boolean test data

#	Boundary Value	#	Boundary Value
1	2	16	" yes "
2	-1	17	" no "
3	99	18	"on "
4	-99	19	" off"
5	0.0	20	"1 "
6	1.0	21	" 0"
7	0.0001	22	"01"
8	-0.0001	23	"00"
9	" true"	24	"10"
10	"false "	25	[]
11	" true "	26	[1]
12	"TRUE\n"	27	{}
13	"FALSE\t"	28	"true" (JSON)
14	"TrUe"	29	"false" (JSON)
15	"FaLsE"	30	5 > 3

Empty boolean test data

#	Empty / Null Value	#	Empty / Null Value
1	null	16	nil
2	NULL	17	DBNull
3	""	18	Optional.empty()
4	" "	19	"\n"
5	" "	20	"null"
6	undefined	21	"NULL"
7	Missing field	22	"undefined"
8	{}	23	Whitespace string
9	Empty CSV value	24	Implicit false default
10	Empty CSV column	25	Implicit true default
11	Field removed	26	Empty request body
12	Field with no value	27	Partial JSON
13	NaN	28	Empty multipart field
14	void	29	Empty form-data field
15	None	30	Short CSV row

Invalid boolean test data

#	Invalid Value	#	Invalid Value
1	"ture"	16	2.5
2	"flase"	17	-2.5
3	"tru"	18	"2"
4	"fal"	19	"-1"
5	"maybe"	20	"ten"
6	"ok"	21	"zero"
7	"cancel"	22	[]
8	"enable"	23	[true, false]
9	"disable"	24	{ "value": true }
10	"truth"	25	function()
11	"falsehood"	26	<true>
12	"truefalse"	27	"✔"
13	"false0"	28	"✖"
14	"yesno"	29	"🙂"
15	"onoff"	30	"SELECT"

Frequently asked questions

Can JSON have Boolean values?

JSON represents Boolean values using true and false. Although 0 and 1 are sometimes used to represent false and true, JSON treats them as numeric values, not Boolean types.

How to pass boolean value in request body?

Boolean values in request bodies depend on the content type being used. JSON and GraphQL support native Boolean values using true and false. In application/x-www-form-urlencoded and multipart/form-data, all values are sent as strings, so Booleans are usually passed as true/false or 0/1, depending on the API. Because of this difference, it is important to verify how the API expects Boolean values to be provided.