support@testinganswers.com
Interview Questions, Answers and Tutorials

Category: Software Testing

Difference between QA and QC

Difference between QA and QCtestinganswers.com
Software testing is a process of verifying and validating that a software application or program meets the business and technical requirements that guided its design and development, and works as expected. Software testing also identifies important defects, flaws, or errors in the application code that must be fixed. Quality means the conformance to the specified design requirement. Being correct, the minimum requirement of quality means performing as required under specified circumstances. Debugging, a narrow view of software testing is performed heavily to find out design defects by the programmer. Quality Assurance (QA) is the process that focuses upon each and…

how to perform Risk Analysis

Software Testingtestinganswers.com2 Comments
Describe how to perform Risk Analysis during software testing. While a test plan is being created, risks involved in testing the product are to be taken into consideration along with the possibility of their occurrence and the damage they may cause along with solutions; if any. A detailed study of this is called Risk Analysis. Some of the risks could be: New Hardware New Technology New Automation Tool The sequence of code delivery Availability of application test resources Identify and describe the risk magnitude indicators: High, Medium, and Low High magnitude means the effect of the risk would be very…

Bug leakage and bug release

Bug Leakage, Bug Releasetestinganswers.com
What is “bug leakage?” and what is “bug release?” A bug leakage results when a bug is detected which should have been detected in earlier builds/versions of the application.A defect which exists during testing yet unfound by the tester which is eventually found by the tester/end-user is also called bug leakage.A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s). These bugs are usually low severity and/or low priority bugs. It is done when the company can afford the existence of bug in the released s/w rather than the time/cost for fixing…