The Test Guide Software Test Guide RSS Feed


Software Testing Knowledgebase

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 


P-use A data use in a predicate
PRINCE2 Projects in Controlled Environments, is a project management method covering the organisation, management and control of projects. PRINCE2 is often used in the UK for all types of projects.
Page Fault A program interruption that occurs when a page that is marked ‘not in real memory’ is referred to by an active page.
Pair programming A software development approach whereby lines of code (production and/or test) of a component are written by two programmers sitting at a single computer.
This implicitly means ongoing real-time code reviews are performed.
Pair testing Two testers work together to find defects. Typically, they share one computer and trade control of it while testing.
Partition Testing A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Pass A test is deemed to pass if its actual result matches its expected result.
Pass/fail criteria Decision rules used to determine whether a test item (function) or feature has passed or failed a test.
Path A sequence of events, e.g. executable statements, of a component or system from an entry point to an exit point.
Path coverage The percentage of paths that have been exercised by a test suite.
Path sensitising Choosing a set of input values to force the execution of a given path.
Path testing A white box test design technique in which test cases are designed to execute paths.
Peer Review A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. A technical review is also known as a peer review.
Performance The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.
Performance indicator A metric, in general high level, indicating to what extent a certain target value or criterion is met. Often related to test process improvement objectives, e.g. Defect Detection Percentage (DDP).
Performance testing The process of testing to determine the performance of a software product.
Performance testing tool A tool to support performance testing and that usually has two main facilities: load generation and test transaction measurement.
Load generation can simulate either multiple users or high volumes of input data. During execution, response time measurements are taken from selected transactions and these are logged.
Performance testing tools normally provide reports based on test logs and graphs of load against response times.
Phase A distinct set of test activities collected into a manageable phase of a project, e.g. the execution activities of a test level.
Plan A document describing the scope, approach, resources and schedule of intended test activities.
Policy A high level document describing the principles, approach and major objectives of the organization regarding testing.
Portability testing The process of testing to determine the portability of a software product.
Postcondition Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.
Precondition Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
Predicted outcome The behaviour predicted by the specification of an object under specified conditions.
Priority The level of (business) importance assigned to an item, e.g. defect.
Problem Domain A specific problem environment for which knowledge is captured in a knowledge base.
Problem Management Process that minimizes the effect on Customer(s) of defects in services and within the infrastructure, human errors and external events.
Process A set of interrelated activities, which transform inputs into outputs.
Process cycle test A black box test design technique in which test cases are designed to execute business procedures and processes.
Production rule Rules are called production rules because new information is produced when the rule fires.
Project A project is a unique set of coordinated and controlled activities with start and finish dates undertaken an objective conforming to specific requirements, including the constraints of time, cost and resources.
Project test plan A test plan that typically addresses multiple test levels.
Prototyping A strategy in system development in which a scaled down system or portion of a system is constructed in a short time, tested, and improved in several iterations.
Pseudo-random A series which appears to be random but is in fact generated according to some prearranged sequence.

© RuleWorks - All Rights Reserved - Policy - - Sitemap