Thread: Why does testing fail?

Hi there!

Since i'm a newbie in the testing field i thought i'd ask the experts out here this question:
Why does testing fail in companies? What are they doing wrong with regards to testing that causes it to fail?

Thanks.
Regards,

Hi again!

Thanks for your response, much appreciated.
Yes, i agree that those are valid reasons.

What about the lack of skill and knowledge on techniques? Or sometimes maybe even the lack of using techniques. Since my understanding would be that techniques are there to help us plan how to test something! I am aware of techniques such as equivelance partitioning, and boundary value analysis. What other good techniques are out there?

Furthermore, what about the fact that many a management dont really understand what testing entails, hence they cannot motivate or point there testers in the direction they should be going?

Thanks.
Regards,

I think to become good tester, first you should be a good developer.

There is nothing called as Fail in testing. If it is the overall application or product that has not met the required demands etc, then that is a different issue altogether like launch to the market or TTM (Time-to-market) etc.
But as far as testing is concerned, some functionality is not working as expected or some requirement has not been met means that the QA team is not effective.
But in real time this does not happen as above the QA team there is another team called Product Management which takes care of such issues.
After all this screening ONLY the product will be launched in the market.

Originally Posted by jainbrijesh

Why you think so?

It's simple , since you know the aspect of development you can put yourself in the developer shoe and think accordingly and can catch bugs much easier.

Any comments

Originally Posted by nsridhara

It's simple , since you know the aspect of development you can put yourself in the developer shoe and think accordingly and can catch bugs much easier.

Any comments

I dont agree with your comment ..
Thinking of developer and Good tester is different..
Developer always tries to make application work .
Tester always tries to BREAK application. .
(Tester can think of scenarios which developer cant. )
Moreover knowledge of product is very important , developer knows only his module but tester should know all the modules and their exact behaviour.

Testing Fails in companies due to many reasons, Not only because of the testing team it fails.

1) Unclear requirements.
2) Communication gap
3) Lack of knowledge about the product.
4) Un realistic time frame.
5) Resource attrition.

i want the answer

its not that testing Fails but its just that thisis an endless process and at some point someone has to take decision to ship it with the known issues.

yeah i agree with most of the comment above but the most imp skill which i feel any manual tester should possess is the Knowledge of the domain in which he is working(which is ignored most of the time),and a very good analytical skill to test different scenarios.
one shold be very strong in basics to make sure he covers most aspect of any product.

But everything said and done thisis also true that its highly impossible (read as not at all possible ) to have a bug free product.
its an incremental process which helps ppl in having a better understanding and more knowledge of the domin which ensures that there won't be any major problem with the build.

Thanks,
Kunals.