Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / 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 |
Post New Answer View All Answers
Explain verification?
Explain a good test engineer?
What is validation and verification testing?
Explain cause-effect graphing?
How do you obtain the expected results for testing a search operation?
What is a software version?
What is system test?
Explain what test plan is? What is the information that should be covered in test plan?
What is the difference between web application and desktop application in the scenario of testing?
How much testing is enough?
viewing entire results after the batch run in qtp Is there is a easier way view the complete results with out opening one by one test scripts
During the testing of a module tester, 'x' found a bug and assigned it to a developer. But developer rejects the same, saying that it's not a bug. What 'x' should do?
What is your primary role in your project?
Which is the current formal world-wide recognized documentation standard?
What is memory leak and defect leak? Is there any harness testing? If yes, please explain?
