Glossary all terms 3.1 / Glossary all terms 3.1: A

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

abuse case
See Also: use case
A use case in which some actors with malcious intent are causing harm to the system or to other actors

#1

acceptance criteria
acceptance testing

#2

accessibility testing
Ref: Gerrard
Testing to determine the ease by which users with disabilities can use a component or system.

#3

account harvesting
The process of obtaining lists of email addresses for use in bulk email messages.

#4

accuracy
Ref: ISO 9126 See Also: functionality
The capability of the software product to provide the right or agreed results or effects with the needed degree of
precision.

#5

accuracy testing
See Also: accuracy
Testing to determine the accuracy of a software product.

#6

acting (IDEAL)
See Also: IDEAL
The phase within the IDEAL model where the improvements are developed, put into practice, and deployed
across the organization. The acting phase consists of the activities: create solution, pilot/test solution, refine
solution and implement solution.

#7

actual result

#8

ad hoc testing
Testing carried out informally. No formal test preparation takes place, no recognized test design technique is
used, there are no expectations for results and arbitrariness guides the test execution activity.

#9

adaptability
Ref: ISO 9126 See Also: portability
The capability of the software product to be adapted for different specified environments without applying
actions or means other than those provided for this purpose for the software considered.

#10

Agile Manifesto
A statement on the values that underpin Agile software development. The values are: individuals and
interactions over processes and tools, working software over comprehensive documentation, customer
collaboration over contract negotiation, responding to change over following a plan.

#11

Agile software development
A group of software development methodologies based on iterative incremental development, where
requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

#12

Agile testing
See Also: test-driven development
Testing practice for a project using Agile software development methodologies, incorporating techniques and
methods, such as extreme programming (XP), treating development as the customer of testing and
emphasizing the test-first design paradigm.

#13

alpha testing

#14

analytical test strategy
A test strategy whereby the test team analyzes the test basis to identify the test conditions to cover.

#15

analytical testing
Testing based on a systematic analysis of e.g., product risks or requirements.

#16

analyzability
Ref: ISO 9126 See Also: maintainability
The capability of the software product to be diagnosed for deficiencies or causes of failures in the software, or
for the parts to be modified to be identified.

#17

anomaly
Ref: IEEE 1044 See Also: defect, error, fault, failure, incident, problem
Any condition that deviates from expectation based on requirements specifications, design documents, user
documents, standards, etc., or from someone's perception or experience. Anomalies may be found during, but
not limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation.

#18

anti-malware
Software that is used to detect and inhibit malware. See also malware.

#19

anti-pattern
Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly
used but is ineffective and/or counterproductive in practice.

#20

API
Acronym for Application Programming Interface.

#21

API testing
Testing performed by submitting commands to the software under test using programming interfaces of the application directly.

#22

assessment report
See Also: process assessment
A document summarizing the assessment results, e.g., conclusions, recommendations and findings.

#23

assessor
A person who conducts an assessment. Any member of an assessment team.

#24

atomic condition
A condition that cannot be decomposed, i.e., a condition that does not contain two or more single conditions
joined by a logical operator (AND, OR, XOR).

#25

attack vector
A path or means by which an attacker can gain access to a system for malicious purposes.

#26

attack-based testing
See Also: fault attack
An experience-based testing technique that uses software attacks to induce failures, particularly security related
failures.

#27

attacker
See Also: hacker
A person or process that attempts to access data, functions or other restricted areas of the system without
authorization, potentially with malicious intent.

#28

attractiveness
Ref: ISO 9126 See Also: usability
The capability of the software product to be attractive to the user.

#29

audit
audit trail
authentication
authorization

#30

audit

#31

automated testware
Testware used in automated testing, such as tool scripts.

#32

automation code defect density
See Also: defect density
Defect density of a component of the test automation code.

#33

availability

#34

Хвилинку...