On Running Crucial Test Data

Blank: See if suitable “error messages” are shown.
Example: ‘’ [i.e., empty.] To avoid this blank error message, we can also provide suggestion as to disable the Submit/any conditional Button. [Example: Login button can be in disabled state until some data is been provided in both Email ID & Password field.]

Valid: Valid input data is properly saved in database. [Data needs to be displayed as per the client requirements.]
Example: (i) For Name field, valid data is “Snacky” & not “159203”.
(ii) For Tax impound, valid data can be “-14,000”, if that is what the client request is.

Invalid: On providing the Negative values & alphanumeric string inputs, you can check for invalid test data. [It depends on that particular field.]
Example: (i) For Name field, invalid data is “159203” & not “Snacky”.
(ii) For Tax impound, invalid data can be “14,000”, if client requires for ‘-ve values’ alone.

Range: Data set which is out of range data. Identify application boundary cases and prepare data set that will cover lower as well as upper boundary conditions.
Example:
In an organization: Recruitment Rules are;
0–15 >> Don’t hire
16–17 >> Can hire on a part-time basis only
18–54 >> Can hire as full-time employees
55–99 >> Don't hire
- What about ages -3 and 101? , this is what range data is all about.

Bulky: This data set should be large in volume.
Example: 60 MB file

Illegal: Make one data set of illegal data format (one set might have symbols). System should not accept illegal data format. ‘Error messages’ should be generated according to the data.
Example: It depends on the file, which you prepare with regards to the data format.