Explore topic-wise InterviewSolutions in .

LATENT defect: This defect is an existing defect in the system which does not cause any failure as the EXACT SET of conditions has never been MET.

Latent defect: This defect is an existing defect in the system which does not cause any failure as the exact set of conditions has never been met.

Phantom is a freeware, and is used for windows GUI automation SCRIPTING language. It allows to take control of windows and functions AUTOMATICALLY. It can simulate any combination of key strokes and mouse clicks as well as MENUS, lists and more.

Phantom is a freeware, and is used for windows GUI automation scripting language. It allows to take control of windows and functions automatically. It can simulate any combination of key strokes and mouse clicks as well as menus, lists and more.

TEST DELIVERABLES are set of documents, tools and other COMPONENTS that has to be developed and maintained in SUPPORT of TESTING.

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

1. Before Testing
2. During Testing
3. After the Testing

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

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

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.

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.

RECORD : Log and handle any PROBLEMS which has happened.

Report: Report the ISSUES to HIGHER level manager.

Control: Define the issue management process.

Record : Log and handle any problems which has happened.

Report: Report the issues to higher level manager.

Control: Define the issue management process.

Retesting: It is a process of checking bugs that are ACTIONED by development team to verify that they are actually FIXED.

DATA Driven TESTING (DDT): In data driven testing process, application is tested with multiple test data. Application is tested with different set of values.

Retesting: It is a process of checking bugs that are actioned by development team to verify that they are actually fixed.

Data Driven Testing (DDT): In data driven testing process, application is tested with multiple test data. Application is tested with different set of values.

System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such TYPE of testing, the application undergoes from beginning till the end.

UAT: USER Acceptance Testing (UAT) involves running a product through a series of SPECIFIC tests which determines whether the product will MEET the needs of its USERS.

System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such type of testing, the application undergoes from beginning till the end.

UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product will meet the needs of its users.

Test design, SCOPE, test strategies , approach are various details that Test plan document consists of:

1. Test CASE identifier
2. Scope
3. Features to be tested
4. Features not to be tested
5. Test STRATEGY & Test approach
6. Test deliverables
7. Responsibilities
8. Staffing and TRAINING
9. Risk and Contingencies

Test design, scope, test strategies , approach are various details that Test plan document consists of:

There are four test levels:

1. Unit/component/program/module TESTING
2. INTEGRATION testing
3. System testing
4. ACCEPTANCE testing

There are four test levels:

Static testing: During Static testing METHOD, the code is not executed and it is performed using the software DOCUMENTATION.

Dynamic testing: To perform this testing the code is REQUIRED to be in an executable FORM.

Static testing: During Static testing method, the code is not executed and it is performed using the software documentation.

Dynamic testing: To perform this testing the code is required to be in an executable form.

In white box testing following steps are verified:

1. Verify the SECURITY holes in the code
2. Verify the incomplete or broken PATHS in the code
3. Verify the flow of structure ACCORDING to the document specification
4. Verify the expected outputs
5. Verify all conditional loops in the code to CHECK the complete functionality of the application
6. Verify the line by line CODING and cover 100% testing

In white box testing following steps are verified:

WHITE box testing technique involves selection of test cases based on an analysis of the INTERNAL structure (Code coverage, branches coverage, paths coverage, condition coverage etc.) of a component or SYSTEM. It is also known as Code-Based testing or STRUCTURAL testing.

Different types of white box testing are:

1. Statement Coverage
2. Decision Coverage

White box testing technique involves selection of test cases based on an analysis of the internal structure (Code coverage, branches coverage, paths coverage, condition coverage etc.) of a component or system. It is also known as Code-Based testing or Structural testing.

Different types of white box testing are:

SDLC DEALS with developement/coding of the software while STLC deales with VALIDATION and verification of the software.

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

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".

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".

Test boundary conditions on, below and above the edges of input and output equivalence classes. For instance, let SAY a bank application where you can WITHDRAW MAXIMUM Rs.20,000 and a minimum of Rs.100, so in boundary value testing we test only the exact boundaries, rather than hitting in the MIDDLE. That means we test above the maximum limit and below the minimum limit.

Test boundary conditions on, below and above the edges of input and output equivalence classes. For instance, let say a bank application where you can withdraw maximum Rs.20,000 and a minimum of Rs.100, so in boundary value testing we test only the exact boundaries, rather than hitting in the middle. That means we test above the maximum limit and below the minimum limit.

Big-Bang TESTING

Big-Bang Testing

SEND to the detailed information of the bug encountered and CHECK the REPRODUCIBILITY.

Send to the detailed information of the bug encountered and check the reproducibility.

EQUIVALENCE PARTITIONING

Equivalence partitioning

IDENTIFYING TEST CONDITIONS and Identifying test CASES.

Identifying test conditions and Identifying test cases.

INEXPENSIVE WAY to GET some BENEFIT.

Inexpensive way to get some benefit.

Scribe

Scribe

FAILURE is a DEPARTURE from SPECIFIED BEHAVIOUR.

Failure is a departure from specified behaviour.

Pre-release testing by END user REPRESENTATIVES at the DEVELOPER's SITE.

Pre-release testing by end user representatives at the developer's site.

The USE of DATA on PATHS through the CODE.

The use of data on paths through the code.

METRICS from previous SIMILAR projects and discussions with the development TEAM.

Metrics from previous similar projects and discussions with the development team.

To measure TEST effectiveness a powerful metric is used to measure test effectiveness known as DRE (DEFECT Removal Efficiency) From this metric we would know how MANY bugs we have found from the set of test cases.

Formula for calculating DRE is:

DRE=Number of bugs while testing / number of bugs while testing + number of bugs found by USER

To measure test effectiveness a powerful metric is used to measure test effectiveness known as DRE (Defect Removal Efficiency) From this metric we would know how many bugs we have found from the set of test cases.

Formula for calculating DRE is:

DRE=Number of bugs while testing / number of bugs while testing + number of bugs found by user

We split TESTING into distinct stages because of following reasons:

1. Each test STAGE has a different purpose
2. It is easier to manage testing in stages
3. We can RUN different test into different environments
4. PERFORMANCE and quality of the testing is improved USING phased testing.

We split testing into distinct stages because of following reasons:

To FREEZE REQUIREMENTS, to understand user needs, to define the scope of testing

To freeze requirements, to understand user needs, to define the scope of testing

During TEST PLANNING

During test planning

Bottom-up INTEGRATION

Bottom-up integration

Because INCREMENTAL integration has better early defects screening and ISOLATION ABILITY.

Because incremental integration has better early defects screening and isolation ability.

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.

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.

Triggered by MODIFICATIONS, MIGRATION or retirement of EXISTING SOFTWARE.

Triggered by modifications, migration or retirement of existing software.

A software development model that illustrates how TESTING ACTIVITIES integrate with software development PHASES.

A software development model that illustrates how testing activities integrate with software development phases.

Because configuration management assures that we KNOW the exact version of the TESTWARE and the test OBJECT.

Because configuration management assures that we know the exact version of the testware and the test object.

It is LED by a TRAINED leader, uses formal entry and EXIT criteria and CHECKLISTS.

It is led by a trained leader, uses formal entry and exit criteria and checklists.

Because ERRORS are frequently MADE during programming of the DIFFERENT cases near the 'edges' of the RANGE of VALUES.

Because errors are frequently made during programming of the different cases near the 'edges' of the range of values.

Regression TESTING should be done on other modules as well because FIXING one MODULE may affect other modules.

Regression testing should be done on other modules as well because fixing one module may affect other modules.

By TESTERS.

By testers.

The techniques of equivalence partitioning and boundary value analysis are often applied to specific situations or inputs. However, if different COMBINATIONS of inputs result in different actions being taken, this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend to be more focused on the user interface. The other two specification-based techniques, decision tables and state transition testing are more focused on BUSINESS LOGIC or business rules. A decision table is a good way to deal with combinations of THINGS (e.g. inputs). This technique is sometimes also referred to as a 'cause-effect' table. The reason for this is that there is an associated logic diagramming technique called 'cause-effect graphing' which was sometimes used to HELP derive the decision table

The techniques of equivalence partitioning and boundary value analysis are often applied to specific situations or inputs. However, if different combinations of inputs result in different actions being taken, this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend to be more focused on the user interface. The other two specification-based techniques, decision tables and state transition testing are more focused on business logic or business rules. A decision table is a good way to deal with combinations of things (e.g. inputs). This technique is sometimes also referred to as a 'cause-effect' table. The reason for this is that there is an associated logic diagramming technique called 'cause-effect graphing' which was sometimes used to help derive the decision table

TECHNICAL REVIEW.

Technical Review.

Black box TESTING is the software testing method which is used to test the software without knowing the internal STRUCTURE of code or program. This testing is usually done to CHECK the functionality of an application. The DIFFERENT black box testing techniques are

1. Equivalence Partitioning
2. BOUNDARY value analysis
3. Cause effect graphing

Black box testing is the software testing method which is used to test the software without knowing the internal structure of code or program. This testing is usually done to check the functionality of an application. The different black box testing techniques are

1 TEST for statement COVERAGE, 2 for BRANCH coverage

1 test for statement coverage, 2 for branch coverage

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.

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.

The main purpose of the integration strategy is to SPECIFY which MODULES to COMBINE when and how many at once.

The main purpose of the integration strategy is to specify which modules to combine when and how many at once.

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

1. Deadlines (Testing, RELEASE)
2. Test budget has been depleted
3. Bug RATE fall below 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.

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

The answer depends on the RISK for your industry, CONTRACT and SPECIAL REQUIREMENTS.

The answer depends on the risk for your industry, contract and special requirements.

LACK of OBJECTIVITY

Lack of Objectivity

Driver

Driver

1899,1900,2004,2005

1899,1900,2004,2005