Explore topic-wise InterviewSolutions in .

A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be TESTED, the testing TASKS, who will do each task, and any RISKS requiring CONTINGENCY planning.

A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

Test-first design is one of the mandatory PRACTICES of Extreme Programming (XP).It REQUIRES that programmers do not write any production code until they have first WRITTEN a UNIT test.

Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

The HARDWARE and software ENVIRONMENT in which tests will be RUN, and any other software with which the software under TEST INTERACTS when under test including stubs and test drivers.

The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

A program or test TOOL USED to execute a tests. ALSO known as a Test HARNESS.

A program or test tool used to execute a tests. Also known as a Test Harness.

An execution environment CONFIGURED for testing. May consist of specific hardware, OS, NETWORK topology, CONFIGURATION of the product under test, other application or system software, etc. The Test Plan for a PROJECT should ENUMERATED the test beds(s) to be used.

An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

The DEGREE to which a system or component facilitates the ESTABLISHMENT of test criteria and the PERFORMANCE of tests to DETERMINE whether those criteria have been met.

The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

Testing based on an ANALYSIS of INTERNAL WORKINGS and structure of a PIECE of software.

Testing based on an analysis of internal workings and structure of a piece of software.

Testing that verifies the program under test stores DATA files in the correct directories and that it RESERVES sufficient space to prevent unexpected termination resulting from lack of space. This is EXTERNAL storage as opposed to internal storage.

Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

A TOOL that CARRIES out STATIC ANALYSIS.

A tool that carries out static analysis.

ANALYSIS of a PROGRAM CARRIED out WITHOUT executing the program. A tool that carries out static analysis.

Analysis of a program carried out without executing the program. A tool that carries out static analysis.

A DELIVERABLE that describes all DATA, FUNCTIONAL and behavioral requirements, all constraints, and all VALIDATION requirements for software

A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software

A pre-release VERSION, which contains the desired functionality of the FINAL version, but which NEEDS to be TESTED for bugs (which ideally should be removed before the final version is released).

A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

A CAUSE of concurrency problems. Multiple accesses to a shared RESOURCE, at least one of which is a write, with no MECHANISM used by EITHER to moderate simultaneous access.

A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

The organizational STRUCTURE, RESPONSIBILITIES, PROCEDURES, PROCESSES, and RESOURCES for implementing quality management.

The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

The OVERALL intentions and DIRECTION of an ORGANIZATION as regards quality as formally EXPRESSED by top management.

The overall intentions and direction of an organization as regards quality as formally expressed by top management.

That ASPECT of the overall management function that determines and IMPLEMENTS the QUALITY policy.

That aspect of the overall management function that determines and implements the quality policy.

A group of INDIVIDUALS with related INTERESTS that meet at regular intervals to CONSIDER problems or other matters related to the QUALITY of OUTPUTS of a process and to the correction of problems or to the improvement of quality.

A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

A systematic and INDEPENDENT examination to determine whether quality activities and related results COMPLY with PLANNED ARRANGEMENTS and whether these arrangements are IMPLEMENTED effectively and are suitable to achieve objectives.

A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

Testing aimed at SHOWING SOFTWARE WORKS. Also KNOWN as "test to pass".

Testing aimed at showing software works. Also known as "test to pass".

TESTING in which all PATHS in the PROGRAM source CODE are tested at LEAST once.

Testing in which all paths in the program source code are tested at least once.

A standard of measurement. SOFTWARE metrics are the statistics describing the structure or content of a PROGRAM. A metric should be a real OBJECTIVE measurement of something such as NUMBER of bugs per lines of code.

A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

A WHITE BOX TESTING technique that exercises program loops.

A white box testing technique that exercises program loops.

This term refers to MAKING SOFTWARE SPECIFICALLY designed for a specific LOCALITY.

This term refers to making software specifically designed for a specific locality.

A group review quality improvement process for WRITTEN MATERIAL. It CONSISTS of two aspects product (document itself) improvement and process improvement (of both document PRODUCTION and inspection).

A group review quality improvement process for written material. It consists of two aspects product (document itself) improvement and process improvement (of both document production and inspection).

A group of PEOPLE WHOSE primary responsibility is SOFTWARE testing.

A group of people whose primary responsibility is software testing.

Black-box TESTS CONDUCTED once the SOFTWARE has been INTEGRATED.

Black-box tests conducted once the software has been integrated.

TESTING ONE PARTICULAR MODULE, FUNCTIONALITY heavily.

Testing one particular module, functionality heavily.

Glass BOX Testing is also known as "WHITE Box Testing" or "Open Box Testing".

It is used to test the EXTERNAL behavior of the Program.This testing is DONE to test the functinality of the APPLICATION.

Glass Box Testing is also known as "White Box Testing" or "Open Box Testing".

It is used to test the external behavior of the Program.This testing is done to test the functinality of the application.

A DOCUMENT that DESCRIBES in detail the CHARACTERISTICS of the product with regard to its intended features.

A document that describes in detail the characteristics of the product with regard to its intended features.

A technique used during PLANNING, analysis and design CREATES a FUNCTIONAL hierarchy for the software.

A technique used during planning, analysis and design creates a functional hierarchy for the software.

Testing which COVERS all combinations of input values and preconditions for an ELEMENT of the SOFTWARE under test.

Testing which covers all combinations of input values and preconditions for an element of the software under test.

A PORTION of a component's INPUT or OUTPUT domains for which the component's BEHAVIOUR is assumed to be the same from the component's specification.

A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

CHECKS for MEMORY leaks or other problems that may OCCUR with prolonged EXECUTION.

Checks for memory leaks or other problems that may occur with prolonged execution.

A device, COMPUTER program, or system that ACCEPTS the same inputs and PRODUCES the same OUTPUTS as a GIVEN system.

A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

TESTING SOFTWARE through EXECUTING it.

Testing software through executing it.

A test that EXERCISES a feature of a PRODUCT in full DETAIL.

A test that exercises a feature of a product in full detail.

Examines an application's requirements for pre-existing software, INITIAL states and CONFIGURATION in ORDER to maintain proper functionality.

Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

Testing of PROGRAMS or procedures used to CONVERT DATA from existing SYSTEMS for use in replacement systems.

Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

The context-driven school of SOFTWARE testing is flavor of Agile Testing that advocates continuous and creative EVALUATION of testing opportunities in light of the potential information REVEALED and the value of that information to the ORGANIZATION RIGHT now.

The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

The PROCESS of testing that an implementation conforms to the specification on which it is BASED. Usually applied to testing conformance to a FORMAL STANDARD.

The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

The GENERATION of SOURCE CODE.

The generation of source code.

A FORMAL testing technique where source code is traced by a GROUP with a small set of TEST cases, while the state of program variables is manually monitored, to analyze the PROGRAMMER's logic and assumptions.

A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

A formal testing technique where the programmer reviews source code with a group who ask QUESTIONS analyzing the program LOGIC, analyzing the code with respect to a checklist of HISTORICALLY common programming errors, and analyzing its compliance with coding STANDARDS.

A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

An analysis METHOD that determines which parts of the software have been executed (COVERED) by the TEST CASE SUITE and which parts have not been executed and therefore may require additional attention.

An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

Phase of DEVELOPMENT where FUNCTIONALITY is IMPLEMENTED in entirety bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

Phase of development where functionality is implemented in entirety bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

A graphical representation of inputs and the associated outputs EFFECTS which can be used to design TEST CASES.

A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

A TEST tool that records test input as it is sent to the software under test. The input cases stored can then be used to REPRODUCE the test at a later time. Most COMMONLY applied to GUI test tools.

A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

COMPUTER AIDED SOFTWARE TESTING.

Computer Aided Software Testing.

A test suite that EXERCISES the full FUNCTIONALITY of a product but does not test FEATURES in DETAIL.

A test suite that exercises the full functionality of a product but does not test features in detail.

TESTING in which all BRANCHES in the program SOURCE CODE are tested at least once.

Testing in which all branches in the program source code are tested at least once.