Glossary all terms 3.1 / Glossary all terms 3.1: P

Власник перекладу встановив такі правила доступу, що ви не можете переглядати чужі варіанти перекладів тут.
Оригінал англійською Переклад українською

pair programming

#1

pair testing
Two persons, e.g., two testers, a developer and a tester, or an end-user and a tester, working together to find defects. Typically, they share one computer and trade control of it while testing.

#2

pairwise integration testing
A form of integration testing that targets pairs of components that work together, as shown in a call graph.

#3

pairwise testing
See Also: combinatorial testing, n-wise testing, orthogonal array testing
A black-box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters.

#4

pass

#5

pass/fail criteria
Ref: IEEE 829
Decision rules used to determine whether a test item (function) or feature has passed or failed a test.

#6

password cracking
Ref: after NIST.IR.7298
A security attack recovering secret passwords stored in a computer system or transmitted over a network.

#7

path

#8

path coverage
The percentage of paths that have been exercised by a test suite. 100% path coverage implies 100% LCSAJ
coverage.

#9

path sensitizing
Choosing a set of input values to force the execution of a given path.

#10

path testing
A white-box test design technique in which test cases are designed to execute paths.

#11

peer review
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 inspection, technical review and walkthrough.

#12

penetration testing
A testing technique aiming to exploit security vulnerabilities (known or unknown) to gain unauthorized access.

#13

performance

#14

performance indicator
Ref: CMMI
Synonyms: key performance indicator
A high-level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g., lead-time slip for software development.

#15

performance profiling

#16

performance testing

#17

performance testing tool

#18

pharming
A security attack intended to redirect a web site's traffic to a fraudulent web site without the user's knowledge or consent.

#19

phase containment
The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced.

#20

phase test plan
See Also: test plan
A test plan that typically addresses one test phase.

#21

phishing
An attempt to acquire personal or sensitive information by masquerading as a trustworthy entity in an electronic communication.

#22

planning poker
See Also: Agile software development, Wideband Delphi
A consensus-based estimation technique, mostly used to estimate effort or relative size of user stories in Agile software development. It is a variation of the Wideband Delphi method using a deck of cards with values representing the units in which the team estimates.

#23

pointer
Ref: IEEE 610
A data item that specifies the location of another data item. For example, a data item that specifies the address of the next employee record to be processed.

#24

portability

#25

portability testing

#26

post-execution comparison

#27

postcondition

#28

precondition

#29

predicate
See Also: decision
A statement that can evaluate to true or false and may be used to determine the control flow of subsequent decision logic.

#30

priority

#31

PRISMA
A systematic approach to risk-based testing that employs product risk identification and analysis to create a product risk matrix based on likelihood and impact. Term is derived from Product RISk MAnagement.

#32

probe effect

#33

procedure testing
Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.

#34

process

#35

process assessment
Ref: after ISO 15504
A disciplined evaluation of an organization's software processes against a reference model.

#36

process cycle test

#37

process improvement

#38

process model
A framework wherein processes of the same nature are classified into a overall model, e.g., a test improvement
model.

#39

process reference model
A process model providing a generic body of best practices and how to improve a process in a prescribed stepby-step
manner.

#40

process-compliant test strategy
A test strategy whereby the test team follows a set of predefined processes, whereby the processes address such items as documentation, the proper identification and use of the test basis and test oracle(s), and the organization of the test team.

#41

process-compliant testing
See Also: standard-compliant testing
Testing that follows a set of defined processes, e.g., defined by an external party such as a standards committee.

#42

process-driven scripting
A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data.

#43

product risk

#44

product-based quality

#45

project

#46

project retrospective
A structured way to capture lessons learned and to create specific action plans for improving on the next project or next project phase.

#47

project risk

#48

pseudo-random
A series which appears to be random but is in fact generated according to some prearranged sequence.

#49

Хвилинку...