Exploratory System Testing - Cheat Sheet
What inputs and data will cause application to perform the most processing? Which inputs might fool application’s error checking routines? Setting of complex preferences or visualization, example completely changing the default UI with additional plug-ins / gadgets available etc. Doing things which don’t make sense from end users perspective. Just do it because it is possible to do. Example – Buy expensive item and return immediately, register into the application and request for removing registration immediately. Do things which only few users would do. Example, create realistically complicated documents, create very complex orders (selection order, # items etc) in shopping cart etc. Identify inputs that are stored and “follow” them around the software. Example – When an address is entered into the shopping site, where does it get displayed? Find features that touch that data and validates the functionality. In a way, try to find life history of objects in the system, like