ISTQB Chapter 2: Testing throughout the software life cycle

Agile Manifesto (2.1)

-individuals & interactions over processes & tools -working software over comprehensive docs -customer collaboration over contract negotiation -respond to change over following a plan

Verification (2.1)

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

Validation (2.1)

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

Performance (2.1)

Degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.

Incremental development model (2.1)

Dev life cycle where a project is broken into increments to deliver requirements.

Iterative development model (2.1)

Dev life cycle where project is broken into a large number of iterations.

V-model (2.1)

Framework to describe the software development life cycle activities from requirements specification to maintenance. Illustrates how testing activities can be integrated into each phase of the life cycle.

Agile software development (2.1)

Group of software dev methodologies based on iterative incremental development, where requirements & solutions evolve through collaboration between self-organizing cross-functioning teams

Test level (2.1)

Group of test activities that are organized and managed together. Linked to responsibilities of a project. example: integration, system, acceptance tests

Integration (2.1)

Process of combining components or systems into larger assemblies.

Efficiency testing (2.2)

Process of testing to determine the efficiency of a software product.

Stub (2.2)

Skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component.

Driver (test driver) (2.2)

Software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.

Commercial Off-The-Shelf (COTS) (2.1)

Software product that's developed for the general market

Component testing (unit/module testing) (2.2)

Testing of individual software components.

Integration testing (2.2)

Testing preformed to expose defects in the interfaces and in the interactions between

Robustness testing (2.2)

Testing to determine the robustness of the software product.

Test driven dev (2.2)

Way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.