what are some good techniques, approaches to find defects in a web based application, which would be found in basic testing?


closed as primarily opinion-based by Bruce McLeod Nov 14 '14 at 3:49

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.


Check out the test heuristics cheat sheet:

This will give you some ideas of what types of things to look for when testing a given type of system. For example, when testing something with an input, do boundary testing (test the limits: what happens when you input nothing? what happens when you input too much data? etc.)


Best approach would be the understand the requirement or the situation and test accordingly.

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

Not the answer you're looking for? Browse other questions tagged or ask your own question.