when we need testing

Question Posted / jareenavennapusa

3 Answers
4861 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

when we need testing..

Answer / dheeraj shandilya

In general testing is a day to day life activity.
We can test everything we do. Testing is needed because we
all make mistake. Some of these mistake are unimportant but
some of them can cause severe damage.
Mistake can be from bad assumptions, blind spot,
misunderstanding, error in use etc.

Is This Answer Correct ?

1 Yes

1 No

when we need testing..

Answer / lakshmanaraj bg

Software testing is the process of identifying the flaws or defects in the system and make sure it is compliant with the client requirements before releasing it to the market.

But testing can never assure 100% bug free software.

This might show the inconsistency and inefficiency of testing process or testing methodologies followed, it could also account the human errors in case of manual testing or script errors in case of automated testing.

This directly impacts the quality of the software.

Hence, in order to improve the software quality, certain protocols and rules need to be laid down and complement the efficiency of the software.

Every software undergoes the risk phase.

Hence risk management is a very important factor which needs to be taken care in order to improve the software quality, reliability and robustness of the software.

Also there should be high amount of transparency as to where the software stands in terms of quality, quantity, progress, user effectiveness, compliance to requirements etc.

This raises an alarm to have a systematic metric and report based process, thus giving rise to test metrics and reports.

Is This Answer Correct ?

0 Yes

0 No

when we need testing..

Answer / sudhansu sekhar panda

According to me we need software testing because of the
following reasons

1) We all can do mistake which leads to deffect and which
leads to failure of the produt

2)In order to avoid the inconsistent between the functional
requirements as well as the actual requirements(i.e
verification against the requirements).

3)S/w testing is a method to identify the
errors/deffects/bugs/issues/flaws inside a product

4)S/W testing is a way which helps to improve the quality.I
found 10000000 bugs once and the developers
chose to fix none of them. So how much did the
quality improve?
- I once worked with developers who introduced 2
bugs for every bug they were trying to fix. I reported
100 bugs, how much did the quality improve?

Thanks
Sudhansu