Printable Flash Cards

Term 1

Agile Testing

Definition 1

Testing practices for projects using (Blank)methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm.

Term 2

Black Box testing

Definition 2

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component confirms to the published requirements for the component.

Term 3

Boundary Testing

Definition 3

Test which focus on the boundary or limit conditions of the software being tested.

Term 4

Bug

Definition 4

A Fault in a program which causes the program in a unintended or unanticipated manner.

Term 5

Coding

Definition 5

The generation of source code.

Term 6

Compatibility Testing

Definition 6

Test whether software is compatible with other elements of a system with which it should operate. e.g. browsers, Operating Systems or hardware.

Term 7

Componet

Definition 7

A minimal software item for which a separate specification is available.

Term 8

Data Dictionary

Definition 8

A database that contains definitions of all data items defined during analysis.

Term 9

Data Flow Diagram

Definition 9

A modeling notation that represents a functional decomposition of a system.

Term 10

Data Driven Testing

Definition 10

Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet

Term 11

Debugging

Definition 11

The process of finding and removing the causes of software failures

Term 12

Defect

Definition 12

Nonconformance to requirements or functional / program specification

Term 13

Functional Specification

Definition 13

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

Term 14

Functional Testing

Definition 14

Testing the features and operational behavior of a product to ensure they correspond to its specifications.

Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

Term 15

Independent Test Group (ITG)

Definition 15

A group of people whose primary responsibility is software testing

Term 16

Integration Testing

Definition 16

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Term 17

Performance Testing

Definition 17

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

Term 18

Quality Control

Definition 18

The operational techniques and the activities used to fulfill and verify requirements of quality.

Term 19

Quality Management

Definition 19

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

Term 20

Regression Testing

Definition 20

Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Term 21

Smoke Testing

Definition 21

A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

Term 22

Software Requirements Specification (SRS)

Definition 22

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

Term 23

System Testing

Definition 23

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Term 24

Test Case

Definition 24

is a commonly used term for a specific test. This is usually the smallest unit of testing. will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.

A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Term 25

Test Environment

Definition 25

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.

Term 26

Test Plan

Definition 26

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.

Term 27

Test Procedure

Definition 27

A document providing detailed instructions for the execution of one or more test cases.

Term 28

Traceability Matrix

Definition 28

A document showing the relationship between Test Requirements and Test Cases.

Term 29

Use Case

Definition 29

The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

Term 30

User Acceptance Testing (UAT)

Definition 30

A formal product evaluation performed by a customer as a condition of purchase.

Term 31

Unit Testing

Definition 31

Testing of individual software components.

Term 32

White Box Testing

Definition 32

Term 33

Software Development Life Cycle (SDLC)

Definition 33

The systems that is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

It includes the following different stages:

1. Requirement phase
2. Design phase
3. Coding (programming)
4. Testing
5. Release (Production)
6. Maintenance (Support)

Term 34

Business Requirement Document (BRD)

Definition 34

It is a document that describes the details of the application functionalities which is required by the user. This document is written by the Business Analysts.

Term 35

Software Testing Life Cycle (STLC)

Definition 35

It starts with study and analyzing the requirements:

1. Requirement Study
2. Test Planning
3. Writing Test Cases
4. Review the Test Cases
5. Executing the Test Cases
6. Bug logging and tracking
7. Close or Reopen bugs

Term 36

Module

Definition 36

is a software component that has a specific task. It can be a ‘link’ which can go inside to its component detail.

Term 37

SQL

Definition 37

stands for Structured Query Language. is an ANSI (American National Standards Institute) standard computer language for accessing and manipulating database systems. statements are used to retrieve and update data in a database. works with database programs like MS Access, DB2, Informix, MS SQL Server, Oracle, Sybase, etc.

Term 38

XML

Definition 38

-stands for EXtensible Markup Language.
-is a markup language much like HTML.
-was designed to describe data.
-tags are not predefined and we must define our own tags.
-uses a Document Type Definition (DTD) or an Schema to describe data.
-with a DTD or XML Schema is designed to be self-descriptive.
-is a W3C Recommendation.

Term 39

Verification

Definition 39

Review process of a requirement

Term 40

Validation

Definition 40

Actual dynamic testing

Term 41

Testing Levels

Definition 41

1. Unit Testing
2. Integration Testing
3. System Testing
4. UAT

Term 42

Performance Testing

Definition 42

To ensure the system is responsive to user interaction.

To test response time and reliability

Term 43

Stress Testing

Definition 43

Executes a system in a manner that demands resources in abnormal quantity, frequency, or volume.

Term 44

Recovery Testing

Definition 44

A system test that forces the software to fail in variety of ways, checks performed

Term 45

Maintenance Testing

Definition 45

Testing changes to existing changes systems and applications which are already in production. Can be an emergency changes.

Term 46

Confirmation Testing

Definition 46

(Re-resting) testing is done after a defect is detected and fixed

Term 47

Static Testing

Definition 47

Refers to testing something that executing. Basically examining and reviewing it.

Term 48

Dynamic Testing

Definition 48

Techniques used are determined by the types of testing that must be detected.

Term 49

Non-Functional Testing

Definition 49

Mostly focuses on anything related to system and applications such as memory leaks, performance, load, stress and reliability.

Term 50

Structural Testing

Definition 50

Concerned with testing the implementation of the program, focuses on the internal structure of the program.

Term 51

Memory Leak

Definition 51

Is present when ever a program loses track of memory.

Term 52

Severity

Definition 52

determines the defect’s effect on the application

Term 53

Priority

Definition 53

Urgent to fix a fault

Term 54

Quality Center

Definition 54

offers software quality assurance, including requirements management, test management and business process testing for IT and application environments.

Term 55

QTP

Definition 55

Professional software provides functional and regression test automation for software applications and environments.

Term 56

SQL Server

Definition 56

A relational database management system (RDBMS) which is part of Microsoft's BackOffice family of servers.

Term 57

What is Acceptance Testing?

Definition 57

Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Term 58

What is Accessibility Testing?

Definition 58

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Term 59

What is Ad Hoc Testing?

Definition 59

A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

Term 60

What is Agile Testing?

Definition 60

Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

Term 61

What is Application Binary Interface (ABI)?

Definition 61

A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

Term 62

What is Application Programming Interface (API)?

Definition 62

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

Term 63

What is Automated Software Quality (ASQ)?

Definition 63

The use of software tools, such as automated testing tools, to improve software quality

Term 64

What is Automated Testing?

Definition 64

Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

Term 65

What is Backus-Naur Form?

Definition 65

A metalanguage used to formally describe the syntax of a language

Term 66

What is Basic Block?

Definition 66

A sequence of one or more consecutive, executable statements containing no branches.

Term 67

What is Basis Path Testing?

Definition 67

A white box test case design technique that uses the algorithmic flow of the program to design tests.

Term 68

What is Basis Set?

Definition 68

The set of tests derived using basis path testing.

Term 69

What is Baseline?

Definition 69

The point at which some deliverable produced during the software engineering process is put under formal change control.

Term 70

What is Beta Testing?

Definition 70

Testing of a rerelease of a software product conducted by customers.

Term 71

What is Binary Portability Testing?

Definition 71

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Term 72

What is Black Box Testing?

Definition 72

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

Term 73

What is Bottom Up Testing?

Definition 73

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.

Term 74

What is Boundary Testing?

Definition 74

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

Term 75

What is Bug?

Definition 75

A fault in a program which causes the program to perform in an unintended or unanticipated manner.

Term 76

What is Defect?

Definition 76

If software misses some feature or function from what is there in requirement it is called as defect.

Term 77

What is Boundary Value Analysis?

Definition 77

BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001

Term 78

What is Branch Testing?

Definition 78

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

Term 79

What is Breadth Testing?

Definition 79

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

Term 80

What is CAST?

Definition 80

Computer Aided Software Testing.

Term 81

What is Capture/Replay Tool?

Definition 81

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.

Term 82

What is CMM?

Definition 82

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes

Term 83

What is Cause Effect Graph?

Definition 83

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

Term 84

What is Code Complete?

Definition 84

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.

Term 85

What is Code Coverage?

Definition 85

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.

Term 86

What is Code Inspection?

Definition 86

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.

Term 87

What is Code Walkthrough?

Definition 87

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.

Term 88

What is Coding?

Definition 88

The generation of source code.

Term 89

What is Compatibility Testing?

Definition 89

Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

Term 90

What is Component?

Definition 90

A minimal software item for which a separate specification is available.

Term 91

What is Component Testing?

Definition 91

Testing of individual software components (Unit Testing).

Term 92

What is Concurrency Testing?

Definition 92

Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Term 93

What is Conformance Testing?

Definition 93

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.

Term 94

What is Context Driven Testing?

Definition 94

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.

Term 95

What is Conversion Testing?

Definition 95

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

Term 96

What is Cyclomatic Complexity?

Definition 96

A measure of the logical complexity of an algorithm, used in white-box testing.

Term 97

What is Data Dictionary?

Definition 97

A database that contains definitions of all data items defined during analysis.

Term 98

What is Data Flow Diagram?

Definition 98

A modeling notation that represents a functional decomposition of a system.

Term 99

What is Data Driven Testing?

Definition 99

Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

Term 100

What is Debugging?

Definition 100

The process of finding and removing the causes of software failures.

Term 101

What is Defect?

Definition 101

Nonconformance to requirements or functional / program specification

Term 102

What is Dependency Testing?

Definition 102

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

Term 103

What is Depth Testing?

Definition 103

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

Term 104

What is Dynamic Testing?

Definition 104

Testing software through executing it. See also Static Testing.

Term 105

What is Emulator?

Definition 105

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

Term 106

What is Endurance Testing?

Definition 106

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

Term 107

What is End-to-End testing?

Definition 107

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Term 108

What is Equivalence Class?

Definition 108

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.

Term 109

What is Equivalence Partitioning?

Definition 109

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

Term 110

What is Exhaustive Testing?

Definition 110

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

Term 111

What is Functional Decomposition?

Definition 111

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

Term 112

What is Functional Specification?

Definition 112

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

Term 113

What is Functional Testing?

Definition 113

Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. or Black Box Testing.

Term 114

What is Glass Box Testing?

Definition 114

A synonym for White Box Testing.

Term 115

What is Gorilla Testing?

Definition 115

Testing one particular module, functionality heavily.

Term 116

What is Gray Box Testing?

Definition 116

A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

Term 117

What is High Order Tests?

Definition 117

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

Term 118

What is Independent Test Group (ITG)?

Definition 118

A group of people whose primary responsibility is software testing,

Term 119

What is Inspection?

Definition 119

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

Term 120

What is Integration Testing?

Definition 120

Term 121

What is Installation Testing?

Definition 121

Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Term 122

What is Localization Testing?

Definition 122

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

Term 123

What is Loop Testing?

Definition 123

A white box testing technique that exercises program loops

Term 124

What is Metric?

Definition 124

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.

Term 125

What is Monkey Testing?

Definition 125

Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

Term 126

What is Negative Testing?

Definition 126

Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

Term 127

What is Path Testing?

Definition 127

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

Term 128

What is Performance Testing?

Definition 128

Term 129

What is Positive Testing?

Definition 129

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

Term 130

What is Quality Assurance?

Definition 130

All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

Term 131

What is Quality Audit?

Definition 131

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.

Term 132

What is Quality Circle?

Definition 132

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.

Term 133

What is Quality Control?

Definition 133

The operational techniques and the activities used to fulfill and verify requirements of quality.

Term 134

What is Quality Management?

Definition 134

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

Term 135

What is Quality Policy?

Definition 135

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

Term 136

What is Quality System?

Definition 136

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

Term 137

What is Race Condition?

Definition 137

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.

Term 138

What is Ramp Testing?

Definition 138

Continuously raising an input signal until the system breaks down.

Term 139

What is Recovery Testing?

Definition 139

Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Term 140

What is Regression Testing?

Definition 140

Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Term 141

What is Release Candidate?

Definition 141

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

Term 142

What is Sanity Testing?

Definition 142

Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

Term 143

What is Scalability Testing?

Definition 143

Performance testing focused on ensuring the application under test gracefully handles increases in work load.

Term 144

What is Security Testing?

Definition 144

Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

Term 145

What is Smoke Testing?

Definition 145

Term 146

What is Soak Testing?

Definition 146

Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

Term 147

What is Software Requirements Specification?

Definition 147

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

Term 148

What is Software Testing?

Definition 148

A set of activities conducted with the intent of finding errors in software.

Term 149

What is Static Analysis?

Definition 149

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

Term 150

What is Static Analyzer?

Definition 150

A tool that carries out static analysis.

Term 151

What is Static Testing?

Definition 151

Analysis of a program carried out without executing the program.

Term 152

What is Storage Testing?

Definition 152

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.

Term 153

What is Stress Testing?

Definition 153

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

Term 154

What is Structural Testing?

Definition 154

Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

Term 155

What is System Testing?

Definition 155

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Term 156

What is Testability?

Definition 156

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.

Term 157

What is Testing?

Definition 157

The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing.

Term 158

What is Test Bed?

Definition 158

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.

Term 159

What is Test Case?

Definition 159

Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

Term 160

What is Test Driver?

Definition 160

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

Term 161

What is Test Environment?

Definition 161

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.

Term 162

What is Test First Design?

Definition 162

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.

Term 163

What is Test Harness?

Definition 163

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

Term 164

What is Test Plan?

Definition 164

Term 165

What is Test Procedure?

Definition 165

A document providing detailed instructions for the execution of one or more test cases

Term 166

What is Test Script?

Definition 166

Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

Term 167

What is Test Specification?

Definition 167

A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

Term 168

What is Test Suite?

Definition 168

A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

Term 169

What is Test Tools?

Definition 169

Computer programs used in the testing of a system, a component of the system, or its documentation.

Term 170

What is Thread Testing?

Definition 170

A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

Term 171

What is Top Down Testing?

Definition 171

An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

Term 172

What is Total Quality Management?

Definition 172

A company commitment to develop a process that achieves high quality product and customer satisfaction.

Term 173

What is Traceability Matrix?

Definition 173

A document showing the relationship between Test Requirements and Test Cases.

Term 174

What is Usability Testing?

Definition 174

Testing the ease with which users can learn and use a product.

Term 175

What is Use Case?

Definition 175

The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities

Term 176

What is Unit Testing?

Definition 176

Testing of individual software components.

Term 177

What is Validation?

Definition 177

The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

Term 178

What is Verification?

Definition 178

The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

Term 179

What is White Box Testing?

Definition 179

Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing.

White box testing is used to test the internal logic of the code.for ex checking whether the path has been executed once, checking whether the branches has been executed at least once .....Used to check the structure of the code.

Term 180

What is Workflow Testing?

Definition 180

Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.

Term 181

Definition 181