Is manually testing a software project for flaws too risky?

Is manually testing a software project for flaws too risky?

What are the factors affecting a manual testing project and what are the ways to overcome it?

    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

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I'm assuming you mean "manual testing" in the context of ethical hacking. Given that you need to consider looking at your app from every possible angle as both an untrusted outsider and a trusted user. Look at things using multiple role levels if you have them. You need to consider what can be thrown at the application in the form of input both in forms and URLs. You'll also want to see what can happen when you disable JavaScript, field length maximums, and so on. A malicious mindset a Web browser are two of the best things you can use to test your Web apps for security flaws so practice, practice, practice.

If you are indeed dealing in terms of "ethical hacking," I can certainly point you in some positive directions and to some good resources. Recently, I have written a number of tips and expert responses dealing with hacking one's own application and or software. Here is a list of a few of them I hope you will find useful.

This was first published in October 2009