Static testing & reviews

The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

A review technique performed informally without a structured process.

A tool that carries out static analysis.

The person involved in the review that identifies and describes anomalies in the product or project under review. Reviewers can be chosen to represent …

A review technique guided by a list of questions or required attributes.

An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules …

The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria …

A form of static analysis based on a representation of unique paths (sequences of events) in the execution through a component or system. Control flow analysis …

A form of static analysis based on the definition and usage of variables.

The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g., test phase. The purpose of entry criteria is to …

An informal usability review in which the reviewers are experts. Experts can be usability experts or subject matter experts, or both.

A software engineering methodology used within Agile software development whereby core practices are programming in pairs, doing extensive code review, unit …

The leader and main person responsible for an inspection or other review process.

A review characterized by documented procedures and requirements, e.g., inspection.

A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the …

A review not based on a formal (documented) procedure.

A type of peer review that relies on visual examination of documents to detect defects, e.g., violations of development standards and non-conformance to higher …

Static analysis aiming to detect and remove malicious code received at an interface.

A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors …

A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are …

A review technique whereby reviewers evaluate the work product from different viewpoints.

The person who records each defect mentioned and any suggestions for process improvement during a review meeting, on a logging form. The scribe should ensure …

An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, …

A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, …

A review technique where reviewers evaluate a work product from the perspective of different stakeholder roles.

A review technique in which a work product is evaluated to determine its ability to address specific scenarios.

Analysis of software development artifacts, e.g., requirements or code, carried out without execution of these software development artifacts. Static analysis …

Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis.

A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content.

A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken.

The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project's goal and the …

A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be …

The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and …

A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria.

A usability testing technique where test participants share their thoughts with the moderator and observers by thinking aloud while they solve usability test …

A document specifying a sequence of actions for the execution of a usability test. It is used by the moderator to keep track of briefing and pre-session …

A test session in usability testing in which a usability test participant is executing tests, moderated by a moderator and observed by a number of observers.

A usability test execution activity specified by the moderator that needs to be accomplished by a usability test participant within a given period of time.