What are some Invalid data inputs that will break a text box?
Mystic last edited by user
I am testing an web-based enterprise application created in Asp.Net. I am testing a text box which accepts alpha-numeric character and maximum 255 chars.
Apart from normal boundary values, nulls, negative data inputs what are some unique, invalid and out of the box data inputs, that will surely crash the application. Some clever ideas in general that will force the application to stall or stop functioning.
morde last edited by user
Honestly, the only limit is your imagination. You'll find out pretty quickly if the programmers took the permissive approach (allow everything except...) or the repressive approach (prevent everything except...)
Some examples you can use:
- Copy/Paste the entire text of Hamlet (thanks to QA Hates You for this one (you'll have to google for it - I don't have access at work)) into the field.
- Drag/Drop the entire text of Hamlet into the field. It's possible someone thought to prevent copy/paste but not drag/drop.
- Try some SQL injection... or code snippets.
- Or HTML
- If there's anything that logically shouldn't be there (like a negative age), try to enter it.
- Change your browser language and input data in that language (or build a virtual with a foreign language keyboard layout and foreign language OS, then use that to enter data - it will catch places where the programmers are using key-press recognition rather than string checks to identify special characters)
- Hold down a key. Does input stop at the field size limit or not?
None of these ideas will necessarily break the application - a really good development team will have limited input in a way that prevents anything not explicitly allowed and then checks and cleans anything that gets through despite their precautions.