How to interpret 'test every scenario you can think of' [closed]

Question

I was recently tasked to,

"Test every scenario you can think of and try to break the component"

What might be sensible in 'everything' when the application is a website?

NOTE: This particular site is ASP.NET with MS-SQL, however, I would like to know what would be covered in general as well. Thank you all for the great responses!

Answer 1

• Every browser in every language
• Every operating system in every language
• A variety of screen resolutions
• Javascript on/off
• Images on/off
• CSS on/off
• Cookies enabled/disabled
• Messing about with URLs
• All sorts of input variations, especially testing for XSS attacks, non-ASCII characters, invalid input
• Keyboard accessibility
• Server related issues - e.g. does the application work OK after a software/hardware restart?
• Opening the site in more than one tab/window is a good way of testing any strange session-related issues

Answer 2

• Try to think of corner cases, and do not forget the common case.
• Stress testing.
• Click every button, and twist every knob on the user interface, make sure the feedback is reasonable and appropriate.
• Try to look at the user interface from every prospective users perspective, are there parts that are confusing, prone to misinterpretation or even do not make sense.
• Take a good look at the metaphors that are used, are they appropriate and used consistently.
• Try gibberish as input.
• Try to input code, e.g. Javascript, make sure it is well protected against hacking attacks.

And of course the basics (copied from Bobby Jack and dr, credit where credits due):

• Every browser
• Every operating system
• Javascript on/off
• Images on/off
• CSS on/off
• Vary screen resolutions
• Cookies enabled