1

Question 1

abnormal end

Answer 1

The unintended termination of the execution of a component or system prior to completion.
a.k.a: abnormal termination

Question 2

abuse case

Answer 2

A use case in which some actors with malicious intent are causing harm to the system or to other actors.

Question 3

acceptance criteria

Answer 3

The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

Question 4

acceptance test-driven development (ATDD)

Answer 4

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which forms the basis for testing a component or system.

Question 5

acceptance testing

Answer 5

A test level that focuses on determining whether to accept the system.

Question 6

accessibility

Answer 6

The degree to which a component or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.

Question 7

accessibility testing

Answer 7

Testing to determine the ease by which users with disabilities can use a component or system.

Question 8

account harvesting

Answer 8

The process of obtaining user account information based on trial and error with the intention or using that information in a security attack.

Question 9

accountability

Answer 9

The degree to which the actions of an entity can be traced uniquely to that entity.

Question 10

accuracy testing

Answer 10

Testing to determine the accuracy of a software product.

Question 11

acting (IDEAL)

Answer 11

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.

Question 12

actor

Answer 12

User or any other person or system that interacts with the test object in specific way.

Question 13

actual result

Answer 13

User or any other person or system that interacts with the test object in a specific way.
a.k.a: actual outcome

Question 14

ad hoc review

Answer 14

A review technique performed informally without a structured process.

Question 15

adaptability

Answer 15

The degree to which a component or system can be adapted for different or evolving hardware, software or other operational or usage environments.

Question 16

agile menifesto

Answer 16

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.

Question 17

agile software development

Answer 17

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

Question 18

agile testing

Answer 18

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.
a.k.a: test-driven development

Question 19

alpha testing

Answer 19

A type of acceptance testing performed in the developer’s test environment by role outside the development.

Question 20

analytical test strategy

Answer 20

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