How will you decide that the software is ready for release?
Please if any one knows this answer, submit the answer as
early as possible.
Answers were Sorted based on User's Feedback
Answer / imthiyaz. shaik
The software release (when to stop testing) depends on the
following factors which would be defined in the Exit
criteria of the Test Plan:
1. The Application/Product should be stable.
2. When all the High severity bugs are fixed.
3. The rate at which the bugs are found is minimal.
4. The project is at minimum risk.
Regards,
Imthiyaz. Shaik
Is This Answer Correct ? | 26 Yes | 2 No |
Answer / gopu
If the software satisfies the customer needs or it passes
acceptance criteria
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / shalini
We will stop at "Test Execution Closure" i.e at whre we
will get stable build
Is This Answer Correct ? | 3 Yes | 0 No |
Answer / jenny chen
We can never really be sure that all errors have been
eliminated. As we found and fixed errors, apart from
customer have satisfied the software, also we have raised
our confidence that software will perform as intended.
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / naveen
If the software ie to be released furninshes all the
requirements that are defined in the Software Requirement
Specification(SRS) and if no bug is present or the high
severity bugs are totally removed.
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / sarika
if the software satisfies the customer need nd its passes
the acceptance criteria and high severity bugs are totally
removed.
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / anshuman
Factors depends on Releasing a Product/Software
1. The Application/Product should be stable and behaving as
per the expectation
2. All High/Medium Severity Issues needs to be resolved and
undergo in QA cycle
3. Regression Harness Execution(If exists) must be in
acceptable conditions (Example - Pass= 96% etc) - This
parameters depends and vary across Organizations
4. Risk involvement must be as low as possible
5. Coverage Matrix/Traceability Matrix should be satisfied
the End-user Needs and shouldn't deviate x% ( Depends on
Organizations Strategy)
6. The Issues which can't be fixed as part of release cycle
should be documented and get it approved by the stack
holder
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / sushant binakar
The software is ready for release after completion of
Testing cycle(when s/w meets its exit criteria ,its testing
is done ) and the requirements of clients are fulfill.
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / sheela
the customer has to satisfied the software. for that
purpose tester should elimated bugs,errors and defaults in
the software then it can be release
Is This Answer Correct ? | 1 Yes | 2 No |
Answer / a.balaji
the product should be stable.
minimising the high severity bugs.
product should accept user interface
assured by qa team
Is This Answer Correct ? | 0 Yes | 1 No |
How do you go about testing a project ?
If a test script instructs WinRunner to open an application to test it, what end conditions might be good?
What is Risk Mitigation and who will involve in Risk mitigation plan?
what is thetesting methodology that u r company folowing??
Whether the testing process followed in different model will be same or will it vary?
wat is ur involvement in test plan
how to do risk analysis during project and during write test cases how to know which one is most crucial functionalities of the application?
Define the bug life cycle?
can we do database testing in manual testing? then how we write the test case?
What is regression testing
what are all the things we will include in " what to be tested and what not to be tested" in Test Plan
When a project was started in an organisation ,Testing team will get BRS & FRS documents and starts preparing the Test cases for the application.when the Build was released whether the Testing team will execute only the written Test cases (or) they may update further testcases