Udemy REST Assured free

Manual Testing Interview Questions

Showing 1 - 10 of 33 results

How we calculate Defect Leakage in Software Testing?


CD = No. of Defects raise by customer after release
DR = No. of Defects raised by Tester before release
ID =  No. of invalid Defects from Defects raised by tester before release(Eg. Duplicate, CannotFix, error in test environment etc.)

Formula to calculate Defect Leakage:

Defect Leakage = [CD / (DR - ID)] * 100

For Example:

If after release client found 9 defects, during the test, tester reported 201 defects and from these 20 defects were invalid, Then,

Defect Leakage = [ 9 / 201 - 20] * 100 = 4.9%

What is Defect Leakage?

After the delivery of application or product or after the release, if end user or Customer find any defect by using that application then it is called defect leakage, it is also called bug leakage.

In short, defect leakage is a metric that measures the percentage of defects leaked from the current testing stage to the subsequent stage as well as proves the effectiveness of testing executed by software testers.

Explain What Does Mobile Security Testing Includes.

  • Checks for multi-user support without interfering with the data between them.
  • Decryption or Encryption method used for sensitive data communication.
  • Checks for access to files stored in the app by any unintended users.
  • Detect sensitive areas in the tested tested application so that they do not receive any malicious content.

Which Tools Are For Performance Testing And Automation?

For performance testing of web services, you can use JMeter. It is an open source tool which can be used to test the API’s performances.

For automation, there are several paid tools available in the market like SeeTest, Ranorex, Silk Mobile etc while free automation tools are Calabash, Appium, Robotium for Android, KIF for iOS.

What Kind of Testing Would You Perform For a General Application?

The very first test we have to perform is installation. After that, we check the basic functionality and following which, we check the connectivity of the application with its peripherals. Then we uninstall the build and verify how the application responds when we interrupt it during installation. We also check interruption scenarios when our application requests a network call.

We also perform low network/poor connectivity testing during a network call. The process of upgrading from an older version to a newer version is also tested. Navigation in the application without a network is an important feature that is tested in general testing. Also, the compatibility of the app on different kinds of phones is a major criterion in general testing.

How Do You Test Patches Intended For An App Already In Production?

We generally do regression testing of a relative module and mainly focus on the area which is related to the bug fixes as per the developer. This is because we cannot perform complete regression testing in a very short span of time. So, we just perform sanity tests on the rest of the application, but only for high priority devices. High priority devices are systems that are running the latest versions of the operating system. 

What is Informal Review ?

An informal review is a way of checking for defects without running code. Informal reviews are implemented many times during the initial stages of the test life cycle of the document. Informal reviews are not documented.

Some key points about Informal Review are:

  • Informal reviews are applied in the early stages of the life cycle of the document.
  • These reviews are conducted between two person team. In later stages more people are involved.
  • The aim of informal reviews is to improve the quality of the document and help the authors.
  • These reviews are not based on the procedure and not documented.

Mention what Requirement Traceability Matrix is?

Requirement Traceability Matrix (RTM) is linking of the requirement documents to test cases. Requirement Traceability Matrix (RTM) is a table (mostly a spreadsheet) which shows if each requirement has a respective Test case / cases to make sure if the requirement is covered for testing. It is basically used to ensure that ALL the requirements and Change Requests are or will be tested.

It is used for the following reason:

  • To ensure that all the application requirements are tested in the verification process
  • To check Test Coverage
Subscribe to Manual Testing Interview Questions