Terms Flashcards
acceptance criteria
The criteria needed to satisfy acceptance
acceptance testing
Testing of requirements to determine whether or not a system satisfies the acceptance criteria
accessibility
Component or system can used by people with the widest range of characteristics and capabilities (disabilities).
accessibility testing
Testing to determine the ease by which users with disabilities can use a component or system.
ad hoc reviewing
Review technique carried out by independent reviewers informally, without a structured process.
Agile software development
A software engineering methodology where core practices are programming in pairs, doing extensive code review, unit testing of all code, and simplicity and clarity in code.
alpha testing
Testing conducted in the developer’s test environment, by roles outside the development organization.
Anoaly
Any condition that deviates from expectation.
audit
Independent examination of a work product, process, or set of processes that is performed by a third party.
availability
The degree to which a component or system is operational and accessible when required for use.
behavior
The response to a set of input values and preconditions.
beta testing
Testing conducted at an external site, by roles outside the development organization.
Synonym: field testing
black-box test technique
Testing the functionality of an application without looking into the code.
boundary value
A minimum or maximum value of an ordered equivalence partition.
EX: Only for ages 18-56
boundary value analysis
A black-box test technique in which test cases are designed based on boundary values.
EX: Only for ages 18-56. Check before 18 and after 56.
burndown chart
Chart that depicts the effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration.
X-axis typically represents days in the sprint.
Y-axis is the remaining effort
Public
checklist-based reviewing
Review guided by a list of questions or required attributes.
checklist-based testing
Experience-based test where the experienced tester uses a high-level list of items to be noted, checked, remembered, or a set of rules or criteria against which a product has to be verified.
code coverage
Analysis method which determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g., statement coverage, decision coverage or condition coverage.
commercial off-the-shelf (COTS)
A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.
compatibility
When a component or system can exchange information with other components or systems.
complexity
When a component or system has a structure that is difficult to understand, maintain and verify.
compliance
The need for software to adhere to standards, conventions or regulations in laws.