Glossary of Terms beginning Alphabet-P
Pair Programming:
Pair Programming is 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:
Pair testing means when two testers work together to find defects. Typically, they share one computer and trade control of it while testing.
Parallel Testing:
Parallel Testing involves testing a new or an altered data processing system with the same source data that is used in another system. The other system is considered as the standard of comparison.
Pass:
A test is deemed to pass if its actual result matches its expected result.
Pass / Fail Criteria:
Pass / Fail Criteria is a set of decision rules formulated to ascertain as to whether the software item or its feature passes or fails a test.
Path:
Path is a sequence of events, e.g. executable statements, of a component or system from an entry point to an exit point.
Path Sensitizing:
Path Sensitizing refers to choosing a set of input values to force the execution of a given path.
Path Testing or Path Coverage:
Path Testing or Path Coverage is a white box method of testing which satisfies the coverage criteria through which the program is tested across each logical path. Usually, paths through the program are grouped into a finite set of classes and one path out of every class is tested. In Path Coverage flow of execution takes place from the start of a method to its exit. Path Coverage ensures that we test all decision outcomes independently of one another
Performance:
Performance is the degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.
Performance Indicator:
Performance Indicator is a high level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g. Defect Detection Percentage (DDP) for testing.
Performance Testing:
Performance Testing is a validation test aimed to ensure that the online response time as well as the batch run time meet the defined performance requirements. Often this is performed using an automated test tool to simulate large number of users. It is also known as “Load Testing”.
Performance Testing Tool:
Performance Testing Tool is 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 Test Plan:
Phase Test Plan is a test plan which typically addresses one test level.
Policy:
Policy is a managerial desires and intents related to either intended objectives of the process or desired attributes of the product.
Population Analysis:
Population Analysis is a process independent of the basic specifications and is aimed at identification of types and frequency of data expected to be processed / produced by the system. The purpose is to verify that the specifications can handle types and frequency of actual data and it can be used further to create validation tests.
Port Testing:
Port Testing is a type of testing in which the test engineer checks as to whether the application is comfortable after deploying it into the client�s original environment or not.
Portability:
Portability is a quality attribute pointing towards the ease with which a software product can be transferred from hardware of one configuration to the other.
Portability Testing:
Portability Testing is the process of testing to determine the portability of a software product.
Positive Testing:
Positive Testing is aimed at showing that the software works. It is also known as “test to pass”.
Post Condition:
Post Condition refers to an environmental and state conditions that must be fulfilled after the execution of a test or test procedure.
Post-execution Comparison:
Post-execution Comparison refers to the comparison of actual and expected results, performed after the software has finished running.
Precondition:
Precondition refers to an environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
Priority:
Priority is the level of (business) importance assigned to an item, e.g. defect.
Procedure:
Procedure is a step-by-step method followed to ensure that the desired standards are followed.
Process:
Process is a set of interrelated activities, which transform inputs into outputs. It is a work effort which produces a product. This includes efforts of the persons and equipment which are guided by the policies, standards and procedures.
Process Cycle Test:
Process Cycle Test is a black box test design technique in which test cases are designed to execute business procedures and processes.
Product:
A product is some thing, which is developed based on the manufacturing company�s specifications and used by multiple customers.
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. In software parlance, It is something developed based on a particular customer requirement and used by that particular customer only.
Project Plan:
Project Plan is 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.
Proof of Correctness:
Proof of Correctness refers to the use of mathematical logical techniques to demonstrate that a relationship between program variables assumed true at the stage of program entry implies that another relationship between program variables holds good at the stage of program exit.
Pseudo Code:
Pseudo Code is a comprehensive set of instructions written in English language & is meant for guiding the actual code developers. These are generally written by the Technical Lead.
Pseudo-Random:
Pseudo-Random refers to a series which appears to be random but is in fact generated according to some prearranged sequence.
Explanation to All Alphabets in the Glossary of Terms
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.