Important Interview Question and Answer for Manual Testing

 

Important QA for manual testing

 

What is "use case testing"?

In order to identify and execute the functional requirement of an application from start to finish "use case" is used and the techniques used to do this is known as "Use Case Testing."

What is the difference between the STLC (Software Testing Life Cycle) and SDLC (Software Development Life Cycle)?

SDLC deals with development/coding of the software while STLC deales with validation and verification of the software

Explain what Test Deliverables is?

Test Deliverables are a set of documents, tools and other components that have to be developed and maintained in support of testing.

There are different test deliverables at every phase of the software development lifecycle

• Before Testing
• During Testing
• After the Testing

What is mutation testing?

Mutation testing is a technique to identify if a set of test data or test case is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.

How will you conduct Risk Analysis?

For the risk analysis following steps need to be implemented

1.   Finding the score of the risk

2.   Making a profile for the risk

3.   Changing the risk properties

4.   Deploy the resources of that test risk

5.   Making a database of risk

What is fault masking explain with example?

When the presence of one defect hides the presence of another defect in the system, it is known as fault masking.

Example: If the "Negative Value" cause a firing of unhandled system exception, the developer will prevent the negative values input. This will resolve the issue and hide the defect of unhandled exception firing. 

What is the difference between Test matrix and Traceability matrix?

·         Test Matrix: Test matrix is used to capture actual quality, effort, the plan, resources and time required to capture all phases of software testing

·         Traceability Matrix: Mapping between test cases and customer requirements is known as Traceability Matrix

 What is the DFD (Data Flow Diagram)?

·         When a "flow of data" through an information system is graphically represented, then it is known as Data Flow Diagram. It is also used for the visualization of data processing. 

Explain what N+1 testing is?

The variation of regression testing is represented as N+1. In this technique, the testing is performed in multiple cycles in which errors found in test cycle 'N' are resolved and re-tested in test cycle N+1. The cycle is repeated unless there are no errors found.

What is Fuzz testing and when it is used?

Fuzz testing is used to detect security loopholes and coding errors in software. In this technique, random data is added to the system in an attempt to crash the system

 Mention what are the categories of defects?

Mainly there are three defect categories

• Wrong: When a requirement is implemented incorrectly
• Missing: It is a variance from the specification, an indication that a specification was not implemented or a requirement of the customer is not met
• Extra: A requirement incorporated into the product that was not given by the end customer. It is considered as a defect because it is a variance from the existing requirements

Mention what the difference between a "defect" and a "failure" in software testing is?

·         In simple terms when a defect reaches the end customer, it is called a failure while the defect is identified internally and resolved; then it is referred to as a defect.

Explain which test cases are written first black boxes or white boxes?

Black box test cases are written first as to write black box test cases; it requires project plan and requirement document all these documents are easily available at the beginning of the project. While writing white box test cases requires more architectural understanding and is not available at the start of the project.

 Explain what the difference between latent and masked defects is?

• Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
• Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed 

What bottom-up testing is?

·         Bottom-up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested. 

Mention what the different types of test coverage techniques are?

Different types of test coverage techniques include

• Statement Coverage: It verifies that each line of source code has been executed and tested
• Decision Coverage: It ensures that every decision in the source code is executed and tested
• Path Coverage: It ensures that every possible route through a given part of the code is executed and tested 

Mention what the meaning of breath testing is?

Breath testing is a test suite that exercises the full functionality of a product but does not test features in detail 

Explain what the meaning of Code Walk Through is?

Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques. 

Mention what the basic components of defect report format are?

The essential components of defect report format include

• Project Name                           
• Module Name                          
• Defect detected on
• Defect detected by
• Defect ID and Name
• Snapshot of the defect
• Priority and Severity status
• Defect resolved by
• Defect resolved on

 Mention what the purpose behind doing end-to-end testing is?

End-to-end testing is done after functional testing. The purpose behind doing end-to-end testing is that

• To validate the software requirements and integration with external interfaces
• Testing application in real-world environment scenario
• Testing of interaction between application and database 

Explain what it means by test harness?

A test harness is configuring a set of tools and test data to test an application in various conditions, and it involves monitoring the output with expected output for correctness. 

What is risk-based testing?

Risk-based Testing is the term used for an approach to creating a Test Strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first 

What is the KEY difference between preventative and reactive approaches to testing?

Preventative tests are designed early; reactive tests are designed after the software has been produced. 

What is the purpose of exit criteria?

The purpose of exit criteria is to define when a test level is completed. 

What the difference between Pilot and Beta testing is?

The difference between a pilot and beta testing is that pilot testing is actually done using the product by the group of users before the final deployment, and in beta testing, we do not input real data, but it is installed at the end customer to validate if the product can be used in production. 

What is component testing?

Component testing, also known as unit, module, and program testing, searches for defects in and verifies the functioning of software (e.g., modules, programs, objects, classes, etc.) that are separately testable. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system. Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components simply. A stub is called from the software component to be tested; a driver calls a component to be tested. 

What is functional system testing?

Testing the end to end functionality of the system as a whole is defined as a functional system testing. 

What are the different Methodologies in Agile Development Model?

There are currently seven different agile methodologies that I am aware of:

1.   Extreme Programming (XP)

2.   Scrum

3.   Lean Software Development

4.   Feature-Driven Development

5.   Agile Unified Process

6.   Crystal

7.   Dynamic Systems Development Model (DSDM) 

What is random/monkey testing? When is it used?

In such type of testing data is generated randomly often using a tool or automated mechanism. With this randomly generated input, the system is tested, and results are analyzed accordingly. These testing are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse effects. 

Consider the following techniques. Which are static and which are dynamic techniques?

1.   Equivalence Partitioning.

2.   Use Case Testing.

3.   Data Flow Analysis.

4.   Exploratory Testing.

5.   Decision Testing.

6.   Inspections.

Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory Testing and Decision Testing are dynamic. 

What are the Structure-based (white-box) testing techniques?

Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works. For example, a structural technique may be concerned with exercising loops in the software. Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the functionality of the software.

 What is negative and positive testing?

A negative test is when you put in an invalid input and receives errors. While positive testing is when you put in a valid input and expect some action to be completed in accordance with the specification.

What are the Experience-based testing techniques?

In experience-based techniques, people's knowledge, skills, and background are a prime contributor to the test conditions and test cases. The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process. Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing.

Could reviews or inspections be considered part of testing?

Yes, because both help detects faults and improves quality. 

When should testing be stopped?

It depends on the risks for the system being tested. There are some criteria based on which you can stop testing.

1.   Deadlines (Testing, Release)

2.   Test budget has been depleted

3.   Bug rate fall below a certain level

4.   Test cases completed with certain percentage passed

5.   Alpha or beta periods for testing ends

6.   Coverage of code, functionality or requirements are met to a specified point

What are semi-random test cases?

Semi-random test cases are nothing, but when we perform random test cases and do equivalence partitioning to those test cases, it removes redundant test cases, thus giving us semi-random test cases. 

What is test coverage?

Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in some other way, e.g., using specification-based techniques). Wherever we can count things and can tell whether or not each of those things has been tested by some test, then we can measure coverage. 

What is the difference between a bug, a defect and an error?

Bug – A bug is a fault in the software that’s detected during testing time. They occur because of some coding error and leads a program to malfunction. They may also lead to a functional issue in the product. These are fatal errors that could block a functionality, results in a crash, or cause performance bottlenecks

Defect – A defect is a variance between expected results and actual results, detected by the developer after the product goes live. Defect is an error found AFTER the application goes into production. In simple terms, it refers to several troubles with the software products, with its external behavior or with its internal features.

Error – An error is a mistake, misunderstanding, or misconception, on the part of a software developer. The category of developer includes software engineers, programmers, analysts, and testers. For example, a developer may misunderstand a design notation, or a programmer might type a variable name incorrectly – leads to an error. An error normally arises in software, it leads to change the functionality of the program. 

What is test closure?

Test Closure is a document which gives a summary of all the tests conducted during the software development life cycle and also gives a detailed analysis of the bugs removed and errors found. This memo contains the aggregate no. of experiments, total no. of experiments executed, total no. of imperfections discovered, add total no. of imperfections settled, total no. of bugs not settled, total no of bugs rejected and so forth.

What is pesticide paradox? How to overcome it?

 

             ·      According to pesticide paradox, if the same tests are repeated over and over again, eventually the same test cases will no longer find new bugs. Developers will be extra careful in those places where testers found more defects and might not look into other areas. Methods to prevent pesticide paradox: 

• To write a whole new set of test cases to exercise different parts of the software. 

•     To prepare new test cases and add them to the existing test cases.    Using these methods, it’s possible to find more defects in the area where defect numbers dropped. 

 What is the difference between Release and Build?

Ans. A build is an executable file provided by the developers to the testing team for testing the application. It undergoes various iterations of fixing and testing until the application works as expected. Once the application becomes stable and ready for the end-users, it’s released in the market.

Whereas, a release is an installable software provided to the end-users after it gets certified by the testing team. During the release of any software to the client, release notes are attached to it that includes a number of defects still open, covered user stories, change-requirements, and version of the release.

What is the difference between bug leakage and bug release?

Ans. Bug leakage is when the tested software is released into the market and the end-user finds bugs in it. These include the bugs that got missed by the testing team during the testing phase.

Whereas, bug release is when a specific version of the software is released in the market with some known bugs which are intended to get fixed in the later versions. These types of issues are of low priority and are mentioned in the release notes while sharing with the end-users.

What do you mean by Defect Triage?

Ans. Defect triage is a process in which the defects are prioritized based on different factors like severity, risk, the time required to fix the bug, etc. The defect triage meeting includes the different stakeholders – the development team, testing team, project manager, BAs, etc, which decide the priority of fixing the defects.

 What is failover testing?

Ans. Failover testing is a type of testing that is used to verify the application’s ability to allocate more resources (more servers) in case of failure and transferring the processing part to the back-up system. 

What is fuzz testing?

Ans. Fuzz testing is a type of testing in which a large amount of random data is provided as input to the application in order to find security loopholes and other issues in the application.

 What is pilot testing?

Ans. Pilot testing is testing carried out as a trial by a limited number of users to evaluate the system and provide their feedback before the complete deployment is carried out.

 What is dev-box Testing?

Ans. In dev-box testing, a tester performs testing on the developer’s system to verify if the major functionalities of the application are stable and ready for testing.

What is the difference between testing and debugging?

Ans. Testing is primarily performed by the testing team in order to find the defects in the system. Whereas, debugging is an activity performed by the development team. In debugging the cause of the defect is located and fixed. Thus removing the defect and preventing any future occurrence of the defect as well.

Another difference between the two is – testing can be done without any internal knowledge of software architecture. Whereas debugging requires knowledge of software architecture and coding.

What is Baseline Testing?

In Baseline testing, a set of tests is run to capture performance information. Baseline testing improves the performance and capabilities of the application by using the information collected and make the changes in the application. Baseline compares the present performance of the application with its previous performance.

What is Benchmark Testing?

Benchmarking testing is the process of comparing application performance with respect to the industry standard given by some other organization.

It is a standard testing which specifies where our application stands with respect to others.