Testing Interview Questions with Answers Test Plan: Test Plan is a document which describes the scope, approach

and schedule of testing activities. Usually a test plan contains following things. 1. 2. 3. 4. 5. 6. 7. 8. Scope of testing Testing approach Time frame Objectives of testing What will be the environment What will be the deliverables Risk factors Features to be tested

Test Strategy: Test Strategy is also document which contains what are all the testing techniques will use to test the application. Testing Techniques are: 1. Black Box Testing 2. White Box Testing 3. Parallel Testing 4. Functionality Testing 5. Regression testing Quality Assurance: QA is Process Oriented Quality Assurance makes sure you are doing the right things, the right way

Quality Control: QC is Product oriented Quality Control makes sure the results of what you've done are what you expected

Alpha Testing: Testing done by developers in development or virtual environment before giving the application to test in testing environment.

Beta Testing: Testing done by clients in real time environment (Not by developers and testers) after the system testing done by testers. UAT Testing: Testing done by customer's end users and they check the product is meeting the requirements or not. Verification: (We build the Product Right?) Process of confirming that application or software meets its specification. Verification appears in initial phase Done through Checklist and walkthrough

Validation: (We Build the right product?) Process of confirming that application or software meets the user requirements Validation appears after the coding phase

Priority: How quickly we need to fix the bug? Or how soon the bug should get fixed? How much the bug is affecting your application testing. Severity: How much the bug is affecting the functionality of the application? 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 informations, but after submitting the form, you get a message like "Order has been cancelled." and Show stopper defect. 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 (Cosmetic Defects) Regression Testing: Test the whole application after any change is made in coding and to make sure those changes does not affect previous functionality. Retesting: Executing the same test case after fixing bug to ensure the bug fixed in the application or not. Types of Testing: Black Box Testing: Tests are based on requirements and functionality Internal system design is not considered in this type of testing.

White Box Testing: Testing is based on knowledge of the internal logic of an applications code. Tests are based on coverage of code statements, branches, paths, conditions

Unit Testing: Testing of individual software components or modules Testing done by the programmer and not by testers, and requires detailed knowledge of the internal program design and code

Integration Testing: Testing of integrated modules to verify combined functionality after integration

System Testing: Testing the entire system based on the requirements.

Acceptance Testing: Testing is done to verify if system meets the customer specified requirements User or customers do this testing to determine whether to accept application

Load Testing: Testing the application under heavy loads and determine what point the system degrades or fails.

Stress Testing: Application is stressed beyond its specifications to check how and when its fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load. Performance Testing: Testing the system response time during navigation to next page and loading of data.

Usability Testing: To check the application is user friendly and proper help documents are documented on that page.

Recovery Testing: Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems

Security Testing: Testing how well the system protects against unauthorized internal or external access And test, database is safe from external attacks.

Compatibility Testing: Testing how well software performs in a particular hardware/software/operating system/network environment and different combinations

Comparison Testing: Comparison of product strengths and weaknesses with previous versions or other similar products

Sanity Testing: Sanity test is used to determine a small section of the application is still working after a minor change.

Sanity test is a narrow regression test that focuses on one or a few areas of functionality Sanity test is usually unscripted.

Smoke Testing: Smoke testing is normal health check up to a build of an application before taking it to testing in depth Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details Smoke test is scripted, either using a written set of tests or an automated test. Agile Testing: Testing will be done, whenever customer requirements are changing dynamically. Boundary Value Analysis: To minimize the test cases we are using Boundary value analysis and Equivalence partitioning If the Text box accepts the number from 1 to 1000 One test case is for 1 and 1000 Second test case for 0 and 999 Third test case is for 2 and 1001 Equivalence Partitioning: To minimize the test cases we are using Boundary value analysis and Equivalence partitioning If the Text box accepts the number from 1 to 1000 One test case is for the value between 1 and 1000 for valid Partition. Second test case for the value 0 (Lower Limit) (Invalid Partition 1) Third test case is for the value 1001 (Higher Limit) (Invalid Partition 2) Cyclomatic Complexity: Used to measure the complexity of the program and provides confidence for a program. Measures the number of linearly independent paths through a Program Source code.

Below mentioned formula is used to measure how many times the program to be executed to execute all statements

C = E-N+2 E No of Edges N No of Nodes V Model: Development and testing takes place at the same time with same kind of information. Development team follow Do Procedure to achieve goals of the company Testing team follow Check Procedure to verify them

Phases in V Model:
Development Customer Requirement Document Software Requirements Specification System Design Unit Design Coding Testing User Acceptance Testing System Testing Integration Testing Unit Testing

Phases in Waterfall Model: Waterfall model is a sequential development process.

Requirement Analysis Design Coding Testing Deployment Maintenance

Spiral Model:

Spiral model the concept of waterfall model is combined with the iterations. After completing one Phase we can easily come back to the previous Phase. This model is mainly implemented in Product based application because cost will be high.

Prototyping Model: A prototype is a working model that is functionally equivalent to a component of the product. Based on the content Model, the developers will create the screens and functionality and testers will test the application. Extreme Programming model:

During planning phase, only Business analyst from client side, effective lead programmer and effective tester will involve. And every couple of weeks, they will show the application development progress and all the activities are visible to the team involved. Customer is in a position to cancel the project if progress is not sufficient. On the other hand, progress is so visible, and the ability to decide what will be done next is so complete.

Statement Coverage: Statement coverage identifies which statements in a method or class have been executed To identify which blocks of code have not been executed. Drawback is, does not identify bugs that arise from the control flow constructs in your source code.

Branch Coverage: A branch is the outcome of a decision, so branch coverage simply measures which decision outcomes have been tested. It takes a more in-depth view of the source code than simple statement coverage