When testing ends?

Hi Frds,


I want to know when testing ends?

thx

Testing ends when all customer expectations are met.

Testing ends when:-

1. There is no more time.
2. There is no more budget.
3. All test cases have been executed.

[b]Otherwise testing never ends......[/b]

[QUOTE=jainbrijesh;12531]Testing ends when:-

1. There is no more time.
2. There is no more budget.
3. All test cases have been executed.

[b]Otherwise testing never ends......[/b][/QUOTE]


Hi,
either when the tests are successfull, what i mean with successful is that they get the output as per the requirement as well as the performace related issues are satisfied.

Testing can also end when the testers find that 80% or so of the test cases fail, then it will go to development team for rework.
:D

Its also true that testing phase never ends, coz client may come up with new reqt, so we need to do testing for the new reqt as well as regression testing to seewhether introduction of these new reqt has effected already running application or not. But we should rather say it, i believe as maintenance phase

1. when all bugs are resolved
2. when the project meets customer requirements and untill we face customer satisfaction.

[QUOTE=bharathi_ark;12584]1. when all bugs are resolved
[/QUOTE]

Dear bharathi,

When bugs get resolved, it again start the tester game of playing with application to get other holes, so you can't say that testing end when bug resolved, even it start with every single bug fix:confused: .

Testing never ends. You need to continuously Imporve your application.
Is Your question need to be specific for one porject?

I agree with jainbrijesh,

But the famous book on testing says that the s/w is under testing even after it goes into production and the s/w is in support stage.:D

I think the book is written by Cem Kanner, I may have spelled his name wrongly.

Thanks Brijesh Jain
For pointout mistake which was made by me.
Now I understood wt mistake i made.

Yes, I agree with you.

This can be difficult to determine. Many modern software applications that complete Testing never be done. Common factors are

1. Deadlines (Testing, Release);

2. Test Cases completed with certain percentage Passed;

3. Test Budget has been depleted;

4. Coverage of the code, functionality, or requirements reaches a specified point;

5. Beta or Alpha Testing period ends.

wen there are no blockers in the aplication,wen there are no major c2"S(type of bugs)wich prevents user frm using the application,though may be if we hav some some c3"s and c4's type of bugs and if deadline is nearer for uat then at this stage testing will be stopeed keeping the above mentioned bugs as known issues

[QUOTE=anandsarpatwari;15311]wen there are no blockers in the aplication,wen there are no major c2"S(type of bugs)wich prevents user frm using the application,though may be if we hav some some c3"s and c4's type of bugs and if deadline is nearer for uat then at this stage testing will be stopeed keeping the above mentioned bugs as known issues[/QUOTE]

What so ever you have described is the points we keep in mind before releasing the product, not to stop testing.

Correct me if I am wrong.

[QUOTE=jainbrijesh;15319]What so ever you have described is the points we keep in mind before releasing the product, not to stop testing.

Correct me if I am wrong.[/QUOTE]

yes ur rite wee keep these bugs as know and will go for uat subject to time deadline is nearer

[QUOTE=anandsarpatwari;15324]yes ur rite wee keep these bugs as know and will go for uat subject to time deadline is nearer[/QUOTE]

So dear anandsarpatwari,

Please post relevant answer as per question.

[quote=kaushal_mit;12497]hi frds, i want to know when testing ends? thx[/quote] we never says that testing is complete. We can stop testing when the following major requiremnts have been met in the application ? 1. When all design test cases have been executed. 2. When high priority bugs have been fixed. 3. When test budget/time is met. 4. When exit creiteria met. 5. When alpha/beta is over.

It is very difficult to determine when this activity will get stop if it is complex application.

When there will be rate of bug falls.
Almost most of the test cases in passed condition.
Budget depleted.
crossing release deadline.

Hope this information will help you. Take care.........

I think it depends on what kind of testing you are doing....and the quality line your of company

:cool:
When [COLOR="Blue"][B]AR = ER[/B][/COLOR]. or we found [COLOR="Blue"][B]zero defect[/B][/COLOR].

This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a specified point
Bug rate falls below a certain level
Beta or alpha testing period ends