Decision Table:
| Valid IP Address | Invalid IP Address |
|---|---|
| All four octets are present and each octet value is between 0-255, separated by dots | One or more octets are missing (e.g. 192..1.1) |
| Examples: 192.168.1.1, 10.10.10.10, 172.16.0.0, 255.255.255.255 | Examples: 192..1.1, 10.10.10., 172..0 |
| One or more octets have an invalid value (e.g. 256.1.1) | |
| Examples: 256.1.1, 10.-1.10, 172.300.0 | |
| Incorrect number of dots (e.g., 192..168..1) | |
| Examples: 192., 192…168., ..168, … | |
| Non-numeric characters (e.g., abc.defg.hijk.lmn) | |
| Examples: abc.defg.hijk.lmn |
Checklist for IP Address “Application”:
- Is the IP address in the form of four octets separated by dots?
- Does each octet have a value between 0-255?
- Are there any missing octets or incorrect number of dots?
- Are there any non-numerical characters in the input?
- Is the IP address within the boundaries of valid inputs?
- Lower Boundaries:
- All octets have a value of 0
- One octet has a value of 0 and the others are non-zero
- One octet has a value of 1 and the others are zero
- Upper Boundaries:
- All octets have a value of 255
- One octet has a value of 254 and the others are 255
- One octet has a value of 255 and the others are 254
- Common Values:
- Random valid IP address
- Random invalid IP address
- Lower Boundaries:




