"I have been assigned to test a UI application page. I have been asked to break the functionality in. The first page is a Sign up page with the following fields: username, password, email, URL address; they all have "check box" selection. I have tried all the ways I can think of to test the page. Could you suggest other possible ways in which we can test the page?"
Requires Free Membership to View
When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.
Hannah Smalltree, Editorial Director
Without knowing specifics this is really tricky to answer. From a functionality perspective you may be at the end of the road. Taking things a step further you can see how a malicious user can manipulate the page. For instance you could see what happens with page submissions when you disable JavaScript, you could manipulate the URL to see if the application returns anything odd, or you could use a Web proxy to capture the page requests/responses in transit to see what you can manipulate and what outcomes that generates. I've found the Firefox Web Developer (https://addons.mozilla.org/en-US/firefox/addon/60) to be a great tool for both functional and security testing of Web applications.
This was first published in September 2009