[Guruji]:- User interface attack # 14
Experiment with invalid operand and operator combinations
· Verifies that computations do not take place with incorrect or invalid data, that the software accounts for more global exception handling
· Ex: divide by zero
· Example: Windows calculator. Take square root of 4 (inverse x2). Then square and subtract 4. Don’t get zero! (close, though). Windows hides the floating point format in rounding the number
User interface attack # 15
Force a function to call itself recursively
· Checks if developer correctly handles the termination case and whether or not an object can interact with itself
· Can manifest itself as an infinite loop
· How to conduct: Find recursive calls and test if there are ways to invoke them
User interface attack # 16
Find features that share data or interact poorly
[Continued in the next day’s post]· These are candidates for errors with integration, especially when we are mixing data types or creating new data structures
· How to conduct: Look at shared features and ask if the same inputs can be applied to each feature in question
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
