Information Technology Reference
In-Depth Information
Output value:
An instance of an output. See also
output
.
Outsourcer:
Company who subcontracts its project to a service provider.
Outsourcing:
Subcontracting a project to a service provider who executes the proj-
ect on behalf of the customer.
P
Pair programming:
A software development approach whereby lines of code
(production and/or test) of a component are written by two programmers sit-
ting at a single computer. This implicitly means ongoing real-time code reviews
are performed.
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.
Partition testing:
See
equivalence partitioning
.
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. [IEEE 829]
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.
100% path coverage implies 100% LCSAJ coverage.
Path sensitizing:
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 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.
Performance:
The degree to which a system or component accomplishes its desig-
nated functions within given constraints regarding processing time and through-
put rate. [IEEE 610] See also
efficiency
.
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). [CMMI]
Performance testing:
The process of testing to determine the performance of a
software product. See also
efficiency testing
.
Performance testing tool:
A tool to support performance testing that usually has
two main facilities: load generation and test transaction measurement. Load gen-
eration 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:
A test plan that typically addresses one test phase. See also
test plan.
