What are the manual testing interview questions and answers?

Answer 1

1. What is baseline testing?Baseline testing is the process of running a set of tests to capture performance information. Baseline testing use the information collected to made the changes in the application to improve performance and capabilities of the application. Baseline compares present performance of application with its own previous performance. 2. What is benchmark testing?Benchmarking testing is the process of comparing application performance with respect to industry standard which is given by some other organization. Benchmark informs us where our application stands with respect to others. Benchmark compares our application performance with other company's application's performance. 3. What is verification and validation?Verification: process of evaluating work-products of a development phase to determine whether they meet the specified requirements for that phase.

Validation: process of evaluating software during or at the end of the development process to determine whether it specified requirements.

Difference between Verification and Validation:

• Verification is Static Testing where as Validations is Dynamic Testing.
• Verification takes place before validation.
• Verification evaluates plans, document, requirements and specification, where as Validation evaluates product.
• Verification inputs are checklist, issues list, walkthroughs and inspection ,where as in Validation testing of actual product.
• Verification output is set of document, plans, specification and requirement documents where as in Validation actual product is output.

4. Explain Branch Coverage and Decision Coverage.Branch Coverage is testing performed in order to ensure that every branch of the software is executed atleast. To perform the Branch coverage testing we take the help of the Control Flow Graph.

Decision coverage testing ensures that every decision taking statement is executed atleast once.

Both decision and branch coverage testing is done to ensure the tester that no branch and decision taking statement, will not lead to failure of the software.

To Calculate Branch Coverage:

Branch Coverage = Tested Decision Outcomes / Total Decision Outcomes.

5. What is difference between Retesting and Regression testing?The differences between Retesting and Regression testing are below:

• Retesting is done to verify defect fix previous in now working correctly where as regression is perform to check if the defect fix have not impacted other functionality that was working fine before doing changes in the code.
• Retesting is specific and is performed on the bug which is fixed where as in regression is not be always specific to any defect fix it is performed when any bug is fixed.
• Retesting concern with executing those test cases that are failed earlier where as regression concern with executing test cases that was passed in earlier builds.
• Retesting has higher priority over regression.

6. What is Mutation testing & when can it be done?Mutation testing is a performed to find out the defect in the program. It is performed to find put bugs in specific module or component of the application. Mutation testing is based on two assumptions:

• Competent programmer hypothesis: according this hypothesis we suppose that program write the correct code of the program.
• Coupling effect: according to this effect collection of different set of test data can also find large and complex bugs.

In this testing we insert few bugs into program to examine the optimal test inputs.

7. What is severity and priority of bug? Give some example.Priority: concern with application from the business point of view.

It answers: How quickly we need to fix the bug? Or how soon the bug should get fixed?

Severity: concern with functionality of application.

How much the bug is affecting the functionality of the application?

Ex.

• High Priority and Low Severity:

  If a company logo is not properly displayed on their website.

• High Priority and High Severity:

  Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."

• Low Priority and High Severity:

  If we have a typical scenario in which the application get crashed, but that scenario exists rarely.

• Low Priority and Low Severity:

  There is a mistake like "You have registered success" instead of successfully, success is written.

8. Explain bug leakage and bug release.Bug Leakage: When customer or end user discovered a bug which can be detected by the testing team. Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.

Bug release: is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances.

9. What is alpha and beta testing?Alpha testing: is performed by the IN-House developers. After alpha testing the software is handed over to software QA team, for additional testing in an environment that is similar to the client environment.

Beta testing: beta testing becomes active. It is performed by end user. So that they can make sure that the product is bug free or working as per the requirement. IN-house developers and software QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.

10. What is Monkey testing?Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.

• Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.
• Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.

Example: In phone number filed Symbols are entered.

11. What is test driver and test stub?

• The Stub is called from the software component to be tested. It is used in top down approach.
• The driver calls a component to be tested. It is used in bottom up approach.
• Both test stub and test driver are dummy software components.

We need test stub and test driver because of following reason:

• Suppose we want to test the interface between modules A and B and we have developed only module A. So we cannot test module A but if a dummy module is prepare, using that we can test module A.
• Now module B cannot send or receive data from module A directly so, in these cases we have to transfer data from one module to another module by some external features. This external feature used is called Driver.

12. What is random testing?When tester performs testing of application by using random input from the input domain of the system, this is Random Testing. Random testing involve following procedures:

• Selection of input domain.
• Randomly selecting any input from input domain.
• Using these test input testing of application is performed.
• The results are compared to the system specification. The test is a failure if any input leads to incorrect results, otherwise it is a success.

13. What is Agile Testing?Agile Testing means to quickly validation of the client requirements and make the application of good quality user interface. When the build is released to the testing team, testing of the application is started to find the bugs. As a Tester, we need to focus on the customer or end user requirements. We put the efforts to deliver the quality product in spite of short time frame which will further help in reducing the cost of development and test feedbacks will be implemented in the code which will avoid the defects coming from the end user. 14. Describe Use Case Testing.Use Case: A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.

Use case Testing: the use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application,

15. What is the purpose of test strategy?We need Test Strategy for the following reasons:

1. To have a signed, sealed, and delivered document, where the document contains details about the testing methodology, test plan, and test cases.

2. Test strategy document tells us how the software product will be tested.

3. Test strategy document helps to review the test plan with the project team members.

4. It describes the roles, responsibilities and the resources required for the test and schedule.

5. When we create a test strategy document, we have to put into writing any testing issues requiring resolution.