Scripted testing ensures the test process is measurable, traceable and repeatable. Security Testing A range of test procedures that attempt to locate vulnerabilities in a system to ensure data and resources are protected from external attacks.
See also penetration testing. Stress Testing Stress testing is a type of load testing carried out to evaluate a system at or beyond the limits of its anticipated levels of load. System Testing System testing is carried out against a complete and integrated system to test that it is functioning as expected and complies with documented requirements. It focuses on the user interface rather than the underlying code. A software product in continuous development will require a different test approach to a small application release.
The test method such as Agile or Waterfall will determine the test approach. It usually forms part of an overall test strategy that deals with the wider issue of quality assurance within an organisation. Test Automation Automated testing is the use of software to execute test cases or other test activities, comparing actual results against expected outcomes.
Test automation can save time and resource needed for manual tests. Or to perform testing that may be too difficult to carry out manually. Automation can improve the reliability and efficiency of a test process.
It can enable a faster release schedule without the bottleneck of repetitive, time consuming manual tests. Test Automation Framework The environment for test automation and usually contains many of the frequently used executions and libraries so that test suites can be established with efficiency. Test Case A test script will be made up of individual test cases, organised into suites. A test case will target a particular piece of functionality in an application and usually contains a set of pre-conditions, inputs, actions, expected results and post-conditions.
For example, a website may have a login page. To verify the login function works as expected, test cases can be created to cover all the tests needed. Test Execution Execution is the process of running tests, either manually or automatically, and logging the results.
Test Plan A test plan is the agreed approach and activities to be carried out together with a schedule for test completion. The test plan is a formal document, central to the test activities and the ultimate point of reference. Test Report A test report is a formal document that is the output of test execution and communicates the results and impacts to the necessary stakeholders. User Acceptance Testing User acceptance testing or UAT is a set of test activities carried out by the end users of a system or software.
UAT is a coordinated and managed activity. It aims to draw out issues that may only be found by real users, using the software in a real environment.
Waterfall In contrast to the iterative nature of an agile approach, the traditional waterfall model follows a more linear process from requirements analysis, design, coding and implementation, through to testing, deployment and maintenance.
While many modern perspectives would focus on the drawbacks of the waterfall model against agile in terms of a lack of flexibility and adaptability, it can still be a suitable approach for single build development projects with shorter timescales.
Where agile often relies less on documentation, Waterfall projects will usually involve a documented test process including test scripts.
See also supplier. A framework for improving process efficiency in systems development and maintenance. Code coverage A generic term for analysis methods that measure the proportion of code in a system that is executed by testing. Code standard Description of how a programming language should be used within an organization. See also naming standard. Compilation The activity of translating lines of code written in a human-readable programming language into machine code that can be executed by the computer.
Component testing Test level that evaluates the smallest elements of the system. See also component. Also known as unit test, program test and module test. Configuration testing A test to confirm that the system works under different configurations of hardware and software, such as testing a website using different browsers.
Context-driven testing Testing which makes use of debugging techniques inspired by real-world usage conditions. It is a method of testing which encourages testers to develop testing opportunities based on the specific details of any given situation.
Software that can be bought on the open market. Daily build A process in which the test object is compiled every day in order to allow daily testing. While it ensures that defect reports are reported early and regularly, it requires automated testing support. Debugging The process in which developers identify, diagnose, and fix errors found.
See also bug and defect. Decision table A test design and requirements specification technique. A decision table describes the logical conditions and rules for a system. Testers use the table as the basis for creating test cases. Defect A flaw in a component or system that can cause the component or system to fail to perform its required function. A defect, if encountered during execution, may cause a failure of the component or system.
Defect report A document used to report a defect in a component, system, or document. Also known as an incident report. Deliverable Any product that must be delivered to someone other than the author of the product.
Examples of deliverables are documentation, code and the system. An iterative development approach. Dynamic testing Testing performed while the system is running. Execution of test cases is one example. End-to-end testing Testing used to test whether the performance of an application from start to finish conforms with the behaviour that is expected from it.
This technique can be used to identify system dependencies and confirm the integrity of data transfer across different system components remains. Entry criteria Criteria that must be met before you can initiate testing, such as that the test cases and test plans are complete. Equivalence partitioning A test design technique based on the fact that data in a system is managed in classes, such as intervals.
Because of this, you only need to test a single value in every equivalence class. For example, you can assume that a calculator performs all addition operations in the same way; so if you test one addition operation, you have tested the entire equivalence class. Execute Run, conduct. When a program is executing, it means that the program is running. When you execute or conduct a test case, you can also say that you are running the test case.
Exhaustive testing A test approach in which you test all possible inputs and outputs. Exit criteria Criteria that must be fulfilled for testing to be considered complete, such as that all high-priority test cases are executed, and that no open high-priority defect remains. Also known as completion criteria. Part of the test case.
See also internal supplier. Extreme programming An agile development methodology that emphasizes the importance of pair programming, where two developers write program code together. The methodology also implies frequent deliveries and automated testing. Failure Deviation of the component or system under test from its expected result.
Fault Injection A technique used to improve test coverage by deliberately inserting faults to test different code paths, especially those that handle errors and which would otherwise be impossible to observe. Formal review A review that proceeds according to a documented review process that may include, for example, review meetings, formal roles, required preparation steps, and goals. Inspection is an example of a formal review. Functional integration An integration testing strategy in which the system is integrated one function at a time.
Gray-box testing Testing which uses a combination of white box and black box testing techniques to carry out software debugging on a system whose code the tester has limited knowledge of.
It includes templates for the test plan, various test reports, and handover documents. Impact analysis Techniques that help assess the impact of a change. Used to determine the choice and extent of regression tests needed. Incident A condition that is different from what is expected, such a deviation from requirements or test cases.
One way to do this is by giving different roles the responsibility for various tests. You can use different sets of test cases to test the system from different points of view. Installation test A type of test meant to assess whether the system meets the requirements for installation and uninstallation. This could include verifying that the correct files are copied to the machine and that a shortcut is created in the application menu. Used when measuring code coverage, for example.
The goal is to find problems in interfaces and communication between components. Internal supplier Developer that belongs to the same organization as the client. The IT department is usually the internal supplier. See also external supplier. ISTQB is responsible for international programs for testing certification. Iteration A development cycle consisting of a number of phases, from formulation of requirements to delivery of part of an IT system.
Common phases are analysis, design, development, and testing. The practice of working in iterations is called iterative development. JUnit A framework for testing Java applications, specifically designed for automated testing of Java components. This makes the source code harder to understand, thus increasing the chance of introducing errors during program development and maintenance. All source code, regardless of the language in which it was programmed, is eventually converted to machine code.
Syn: object code. IEEE In software engineering, a predefined sequence of computer instructions that is inserted into a program, usually during assembly or compilation, at each place that its corresponding macroinstruction appears in the program. IEEE A source code instruction that is replaced by a predefined sequence of source instructions, usually in the same language as the rest of the program and usually during assembly or compilation.
A non-moving storage device utilizing one of a number of types of electronic circuitry to store information. IEEE A software component that is called by the operating system of a computer and that usually calls other software components. See: routine, subprogram.
IEEE The ease with which a software system or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment. Syn: modifiability. QA Activities such as adjusting, cleaning, modifying, overhauling equipment to assure performance in accordance with requirements.
Maintenance to a software system includes correcting software errors, adapting software to a new environment, or making enhancements to software. See: adaptive maintenance, corrective maintenance, perfective maintenance. A measure of the reliability of a computer system, equal to average operating time of equipment between failures, as calculated on a statistical basis from the known failure rates of various components of the system.
A measure of reliability, giving the average time before the first failure. A measure of reliability of a piece of repairable equipment, giving the average time between repairs. IEEE A quantitative assessment of the degree to which a software product or process possesses a given attribute. The process of determining the value of some quantity in terms of a standard unit.
Approximately one million bits. Precisely K bits, bits, or 1,, bits. Approximately one million bytes. Precisely K Bytes, bytes, or 1,, bytes. See: kilobyte. Any device or recording medium into which binary data can be stored and held, and from which the entire original data can be retrieved. The two types of memory are main; e. See: storage device.
A computer display listing a number of options; e. Sometimes used to denote a list of programs. One of two major categories of chip design [the other is bipolar]. It derives its name from its use of metal, oxide and semiconductor layers.
Common type of transistor fabricated as a discrete component or into MOS integrated circuits. NBS The process of generating test sets for structural testing based upon use of complexity metrics or coverage metrics.
IEEE A quantitative measure of the degree to which software possesses a given attribute which affects its quality. Communications network that covers a geographical area such as a city or a suburb. Permanent memory that holds the elementary circuit operations a computer must perform for each instruction in its instruction set.
Frequently synonymous with a microcomputer. Execution speed of a computer. MIPS rate is one factor in overall performance. Bus and channel speed and bandwidth, memory speed, memory management techniques, and system software also determine total throughput. DOD An unplanned event or series of events resulting in death, injury, occupational illness, or damage to or loss of data and equipment or property, or damage to the environment.
Syn: accident. A symbol chosen to assist human memory and understanding; e. Construction of programs used to model the effects of a postulated environment for investigating the dimensions of a problem for the effects of algorithmic processes on responsive targets. ISO A functional unit that modulates and demodulates signals. One of the functions of a modem is to enable digital data to be transmitted over analog transmission facilities.
The term is a contraction of modulator-demodulator. Using a modem to communicate between computers. MODEM access is often used between a remote location and a computer that has a master database and applications software, the host computer. A structured software design technique, breaking a system into components to facilitate design and development. Syn: functional decomposition, hierarchical decomposition. See: abstraction. IEEE Software composed of discrete parts. See: structured design.
IEEE The degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components.
Varying the characteristics of a wave in accordance with another wave or signal, usually to make user equipment signals compatible with communication facilities. Contrast with demodulate. Converting signals from a binary-digit pattern [pulse form] to a continuous wave form [analog].
Contrast with demodulation. See: unit. A table which provides a graphic illustration of the data elements whose values are input to and output from a module. IEEE A mode of operation in which two or more processes [programs] are executed concurrently [simultaneously] by separate CPUs that have access to a common main memory.
Contrast with multi-programming. See: multi-tasking, time sharing. Syn: parallel processing. Contrast with multi-tasking. See: time sharing. IEEE A mode of operation in which two or more tasks are executed in an interleaved manner.
See: multi-processing, multi-programming, time sharing. Myers A test coverage criteria which requires enough test cases such that all possible combinations of condition outcomes in each decision, and all points of entry, are invoked at least once.
Contrast with branch coverage, condition coverage, decision coverage, path coverage, statement coverage. A device which takes information from any of several sources and places it on a single line or sends it to a single destination. IEEE Computer systems that perform more than one primary function or task are considered to be multipurpose. In some situations the computer may be linked or networked with other computers that are used for administrative functions; e.
NBS A method to determine test set thoroughness by measuring the extent to which a test set can discriminate the program from slight variants [mutants] of the program. Contrast with error seeding. National Bureau of Standards. Now National Institute for Standards and Technology. National Institute for Standards and Technology. Gaithersburg, MD A federal agency under the Department of Commerce, originally established by an act of Congress on March 3, as the National Bureau of Standards.
The Institute's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. The National Computer Systems Laboratory conducts research and provides, among other things, the technical foundation for computer related policies of the Federal Government. A type of microelectronic circuit used for logic and memory chips. A database organization method that allows for data relationships in a net-like form.
A single data element can point to multiple data elements and can itself be pointed to by other data elements. Contrast with relational database.
A junction or connection point in a network, e. IEEE 1 Examines software elements that are not designated safety-critical and ensures that these elements do not cause a hazard. Generally, safety-critical code should be isolated from non-safety-critical code. This analysis is to show this isolation is complete and that interfaces between safety-critical code and non-safety-critical code do not create hazards.
A reformation of a program by immediately relinking the entire program following the testing of each independent module.
Integration testing is then conducted on the program as a whole. Syn: "big bang" integration. Contrast with incremental integration. A high priority interrupt that cannot be disabled by another interrupt. It can be used to report malfunctions such as parity, bus, and math co-processor errors. IEEE A value whose definition is to be supplied within the context of a specific operating system. This value is a representation of the set of no numbers or no value for the operating system in use.
IEEE Data for which space is allocated but for which no value currently exists. IEEE A string containing no entries. Note: It is said that a null string has length zero.
In object oriented programming, A self contained module [encapsulation] of data and the programs [services] that manipulate [process] that data. NIST A code expressed in machine language ["1"s and "0"s] which is normally an output of a given translation process that is ready to be executed by a computer. Syn: machine code. Contrast with source code.
See: object program. IEEE A software development technique in which a system or component is expressed in terms of objects and connections between those objects. IEEE A programming language that allows the user to express a program in terms of objects and messages between those objects.
A technology for writing programs that are made up of self-sufficient modules that contain all of the information needed to manipulate a given data structure. The modules are created in class hierarchies so that the code or methods of a class can be passed to other modules. New object modules can be easily created by inheriting the characteristics of existing classes. See: object, object oriented design.
IEEE A computer program that is the output of an assembler or compiler. IEEE Pertaining to a system or mode of operation in which input data enter the computer directly from the point of origin or output data are transmitted directly to the point where they are used.
For example, an airline reservation system. See: conversational, interactive, real time. Usually, operating systems are predominantly software, but partial or complete hardware implementations are possible. IEEE The period of time in the software life cycle during which a software product is employed in its operational environment, monitored for satisfactory performance, and modified as necessary to correct problems or to respond to changing requirements.
IEEE An exception that occurs when a program encounters an invalid operation code. An information processing technology that converts human readable data into another medium for computer input. An OCR peripheral device accepts a printed document as input, to identify the characters by their shape from the light that is reflected and creates an output disk file. For best results, the printed page must contain only characters of a type that are easily read by the OCR device and located on the page within certain margins.
When choosing an OCR product, the prime consideration should be the program's level of accuracy as it applies to the type of document to be scanned. Thin glass wire designed for light transmission, capable of transmitting billions of bits per second. Unlike electrical pulses, light pulses are not affected by random radiation in the environment. NIST Modifying a program to improve performance; e. A relational database programming system incorporating the SQL programming language.
A registered trademark of the Oracle Corp. ISO In a calculator, the state in which the calculator is unable to accept or process the number of digits in the entry or in the result. See: arithmetic overflow. IEEE An exception that occurs when the result of an arithmetic operation exceeds the size of the storage location designated to receive it. Contrast with serial. IEEE A constant, variable or expression that is used to pass values between software modules.
Syn: argument. An error detection method in data transmissions that consists of selectively adding a 1-bit to bit patterns [word, byte, character, message] to cause the bit patterns to have either an odd number of 1-bits [odd parity] or an even number of 1-bits [even parity]. ISO A binary digit appended to a group of binary digits to make the sum of all the digits, including the appended binary digit, either odd or even, as predetermined.
ISO A redundancy check by which a recalculated parity bit is compared to the predetermined parity bit. Contrast with check summation, cyclic redundancy check [CRC]. A high-level programming language designed to encourage structured programming practices.
ISO A character string that enables a user to have full or limited access to a system or to a set of data. IEEE A change made directly to an object program without reassembling or recompiling from the source program. IEEE A sequence of instructions that may be performed in the execution of a computer program. IEEE Analysis of a computer program [source code] to identify all possible paths through the program, to detect incomplete paths, or to discover portions of the program that are not on any path.
IEEE Software maintenance performed to improve the performance, maintainability, or other attributes of a computer program. Contrast with adaptive maintenance, corrective maintenance. IEEE A requirement that imposes conditions on a functional requirement; e. Equipment that is directly connected a computer. A peripheral device can be used to input data; e. Syn: peripheral equipment. Synonymous with microcomputer, a computer that is functionally similar to large computers, but serves only one user.
IEEE An audit conducted to verify that a configuration item, as built, conforms to the technical documentation that defines it. See: functional configuration audit. IEEE A requirement that specifies a physical characteristic that a system or system component must posses; e.
IEEE 1 In image processing and pattern recognition, the smallest element of a digital image that can be assigned a gray level. This term is derived from the term "picture element". The hardware and software which must be present and functioning for an application program to run [perform] as intended.
A technique a CPU can use to learn if a peripheral device is ready to receive data or to send data. In this method each device is checked or polled in-turn to determine if that device needs service. The device must wait until it is polled in order to send or receive data. This method is useful if the device's data can wait for a period of time before being processed, since each device must await its turn in the polling scheme before it will be serviced by the processor.
Contrast with interrupt. A type of microelectronic circuit in which the base material is positively charged. The relative degree of repeatability, i. It is the result of resolution and stability. See: accuracy, bias, calibration. IEEE 1 The process of analyzing design alternatives and defining the architecture, components, interfaces, and timing and sizing estimates for a system or component. See: detailed design. IEEE A review conducted to evaluate the progress, technical adequacy, and risk resolution of the selected design approach for one or more configuration items; to determine each design's compatibility with the requirements for the configuration item; to evaluate the degree of definition and assess the technical risk associated with the selected manufacturing methods and processes; to establish the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment, facilities, software and personnel; and, as applicable, to evaluate the preliminary operational and support documents.
A flat board that holds chips and other electronic components. The board is "printed" with electrically conductive pathways between the components. The computer file that contains the establishment's current production data.
Processing may include the use of an assembler, a compiler, an interpreter, or another translator to prepare the program for execution. The instructions may include statements and necessary declarations. IEEE A specification language with special constructs and, sometimes, verification protocols, used to develop, analyze, and document a program design.
IEEE A computer program that has been purposely altered from the intended version to evaluate the ability of program test cases to detect the alteration. See: testing, mutation. A programmable logic chip.
See: programmable logic device. A logic chip that is programmed at the user's site. Contrast with PROM. A chip which may be programmed by using a PROM programming device. It can be programmed only once. It cannot be erased and reprogrammed. Each of its bit locations is a fusible link. An unprogrammed PROM has all links closed establishing a known state of each bit. Programming the chip consists of sending an electrical current of a specified size through each link which is to be changed to the alternate state.
This causes the "fuse to blow", opening that link. IEEE A language used to express computer programs. See: computer language, high-level language, low-level language. IEEE Analysis to ensure that all portions of the program follow approved programming guidelines. See: code audit, code inspection. NIST A management document describing the approach taken for a project. The plan typically describes work to be done, resources required, methods to be used, the configuration management and quality assurance procedures to be followed, the schedules to be met, the project organization, etc.
Project in this context is a generic term. Some projects may also need integration plans, security plans, test plans, quality assurance plans, etc. See: documentation plan, software development plan, test plan, software engineering. PROM programmer. NBS The use of techniques of mathematical logic to infer that a relation between program variables assumed true at program entry implies that another relation between program variables holds at program exit.
IEEE An exception that occurs when a program attempts to write into a protected area in storage. ISO A set of semantic and syntactic rules that determines the behavior of functional units in achieving communication.
Using software tools to accelerate the software development process by facilitating the identification of required functionality during analysis and design phases.
A limitation of this technique is the identification of system or software problems and hazards. See: rapid prototyping. A combination of programming language and natural language used to express a software design. If used, it is usually the last document produced prior to writing the source code. FDA Establishing confidence that process equipment and ancillary systems are compliant with appropriate codes and approved design intentions, and that manufacturer's recommendations are suitably considered.
FDA Establishing confidence that process equipment and sub-systems are capable of consistently operating within established limits and tolerances. FDA Establishing confidence that the process is effective and reproducible. FDA Establishing confidence through appropriate testing that the finished product produced by a specified process meets all release requirements for functionality and safety. IEEE 1 A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements.
The operational techniques and procedures used to achieve quality requirements. High frequency electromagnetic waves that emanate from electronic devices such as chips and other electronic devices. An electromagnetic disturbance caused by such radiating and transmitting sources as electrostatic discharge [ESD], lightning, radar, radio and TV signals, and motors with brushes can induce unwanted voltages in electronic circuits, damage components and cause malfunctions.
See: electromagnetic interference. The term random access means that each memory location [usually 8 bits or 1 byte] may be directly accessed [read from or written to] at random.
ISO A limit check in which both high and low values are stipulated. A structured software requirements discovery technique which emphasizes generating prototypes early in the development process to permit early feedback and analysis in support of the development process. Contrast with incremental development, spiral model, waterfall model. See: prototyping. A memory chip from which data can only be read by the CPU.
The CPU may not store data to this memory. IEEE Pertaining to a system or mode of operation in which computation is performed during the actual time that an external process occurs, in order that the computation results can be used to control, monitor, or respond in a timely manner to the external process. See: conversational, interactive, interrupt, on-line. A fast-response [immediate response] on-line system which obtains data from an activity or a physical process, performs computations, and returns a response rapidly enough to affect [control] the outcome of the activity or process; e.
Contrast with batch processing. Documentation of changes made to the system. A record of change can be a written document or a database. Normally there are two associated with a computer system, hardware and software.
Changes made to the data are recorded in an audit trail. IEEE 1 The process of defining or generating a process or data structure in terms of itself. Computer architecture that reduces the complexity of the chip by using simpler instructions.
Reduced instruction set does not necessarily mean fewer instructions, but rather a return to simple instructions requiring only one or a very few instruction cycles to execute, and therefore are more effectively utilized with innovative architectural and compiler changes. Systems using RISC technology are able to achieve processing speeds of more than five million instructions per second.
Regions are used to separate testing from production [normal use]. Syn: partition. A small, high speed memory circuit within a microprocessor that holds addresses and values of internal operations; e. Each microprocessor has a specific number of registers depending upon its design. See: testing, regression. Database organization method that links files together as required.
Relationships between files are created by comparing data such as account numbers and names. A relational system can take any two or more files and generate a new file from the records that meet the matching criteria.
Routine queries often involve more than one data file; e. Contrast with network database, flat file. IEEE The formal notification and distribution of an approved version. See: version. IEEE The ability of a system or component to perform its required functions under stated conditions for a specified period of time.
See: software reliability. IEEE 1 A condition or capability needed by a user to solve a problem or achieve an objective. See: design requirement, functional requirement, implementation requirement, interface requirement, performance requirement, physical requirement. IEEE 1 The process of studying user needs to arrive at a definition of a system, hardware, or software requirements.
See also Test Driven Development. Application Binary Interface ABI : A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.
Application Programming Interface API : 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. Automated Software Quality ASQ : The use of software tools, such as automated testing tools, to improve software quality. Backus-Naur Form: A metalanguage used to formally describe the syntax of a language. Basic Block: A sequence of one or more consecutive, executable statements containing no branches.
Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests. Basis Set: The set of tests derived using basis path testing. Baseline: The point at which some deliverable produced during the software engineering process is put under formal change control. Benchmark Testing: Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration.
Beta Testing: Testing of a rerelease of a software product conducted by customers. Binary Portability Testing: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification. Black Box Testing: 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.
Bottom Up Testing: 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. Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested.
Some of these tests are stress tests. Boundary Value Analysis: In boundary value analysis, test cases are generated using the extremes of the input domaini, e.
BVA is similar to Equivalence Partitioning but focuses on "corner cases". Branch Testing: Testing in which all branches in the program source code are tested at least once. Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail. Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner.
The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools. Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.
Code Complete: 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. Code Coverage: 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. Code Inspection: 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.
Code Walkthrough: 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. Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.
Component: A minimal software item for which a separate specification is available. Component Testing: See Unit Testing. Concurrency Testing: 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. Conformance Testing: 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. Context Driven Testing: 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. Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Cyclomatic Complexity: A measure of the logical complexity of an algorithm, used in white-box testing. Data Dictionary: A database that contains definitions of all data items defined during analysis.
Data Flow Diagram: A modeling notation that represents a functional decomposition of a system.
0コメント