ISTQB GLOSSARY 2014 PDF

We have defined a glossary in order to clarify the Terms, Definitions, and Acronyms which will be used during the lifecycle of the project. The document can be downloaded from here. Abstract test case : a complete and independent specification of the actions required to achieve a specific test purpose. An abstract test case may be represented as a set of informal instructions or as a formal specification like a TTCN-3 test case. Accuracy: the capability of the software product to provide the right or agreed results or effects with the needed degree of precision.

Author:Kakazahn Shasar
Country:New Zealand
Language:English (Spanish)
Genre:Career
Published (Last):10 November 2004
Pages:233
PDF File Size:2.25 Mb
ePub File Size:5.52 Mb
ISBN:393-7-26809-136-8
Downloads:76747
Price:Free* [*Free Regsitration Required]
Uploader:Tukazahn



We have defined a glossary in order to clarify the Terms, Definitions, and Acronyms which will be used during the lifecycle of the project. The document can be downloaded from here. Abstract test case : a complete and independent specification of the actions required to achieve a specific test purpose. An abstract test case may be represented as a set of informal instructions or as a formal specification like a TTCN-3 test case. Accuracy: the capability of the software product to provide the right or agreed results or effects with the needed degree of precision.

ISO Accuracy test case : a test case that determines the accuracy of a software product. Abstract test suite : a test suite composed of abstract test cases. All-pairs testing : see pairwise testing.

Application Programming Interface: a protocol intended to be used as an interface by software components to communicate with each other.

Black-box testing : testing, either functional or non-functional, without reference to the internal structure of the component or system. Black-box test execution: black-box test execution stimulates and observes the system under test solely at its public interfaces.

Any utility concept that helps evaluating the internal state of the system under test except the publicly available interfaces must not be used during a strict black-box test execution. Boundary-value: a n input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range.

Boundary-value analysis : a black box test design technique in which test cases are designed based on boundary values. Cloud deployment model: model of the activities that make a Cloud available for use. Cloud providers may use one of four different deployment models: private cloud, community cloud, public cloud, and hybrid cloud.

Cloud provider : is a service provider that offers customers storage or software services available via a private private cloud or public network public cloud. The storage and software are available for access via the Internet and the cloud provider manages the infrastructure and platforms on which the applications run. Cloud service model: model of offers of Cloud services. Code coverage : an analysis method that determines which parts of the software have been executed covered by the test suite and which parts have not been executed, e.

Combinatorial test design methods : test design methods whose purposes identify the minimum number of tests needed to get coverage.

Community Cloud : a cloud deployment model where the provider makes applications, storage, and other resources available to a specific community of consumers from organizations that have shared concerns e. It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.

Coverage : the degree, expressed as a percentage, to which a test suite has exercised a specified coverage item. Veenendaal Defect: a flaw in a component or system that can cause the component or system to fail to ATM perform its required function, e. A defect, if encountered during execution, may cause a failure of the component or system.

Design for testability : Increasing the degree of testability of a system by applying respective development process measures. Emulator: a device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

IEEE Std. Equivalence partitioning : a black box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle test cases are designed to cover each partition at least once. Error : a human action that produces an incorrect result. Event: an observable action of a software that is characterized by its type and its target, e.

Failure : deviation of the component or system from its expected delivery, service or result. False negative : f ail test verdict in presence of no SUT failures. False positive : pass test verdict in presence of SUT failures. Functional Testing : testing based on an analysis of the specification of the functionality of a component or system.

See also black-box testing. Fuzzing : see Fuzz testing. Fuzz testing : technique for intelligently and automatically generating and passing into a target system valid and invalid message sequences to see if the system breaks, and if it does, what it is that makes it break. Generic service: a service whose operations are generic, i. Graphical User Interface: a type of user interface that allows users to interact with electronic devices using images rather than text commands.

Grey-box testing : testing that combines black-box testing and white-box testing principles. Hybrid Cloud : a cloud deployment model combining two or more distinct cloud infrastructures private, community, or public that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability.

Multiple instances of a variety of operating systems may share the virtualized hardware resources. See also system under test SUT. Infrastructure as a Service IaaS : a cloud service model, in which cloud providers offer processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications.

The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications; and possibly limited control of selecting networking components.

Interface: a hardware or software component that connects two or more other components for the purpose of passing information from one to the other. Internet of Services : a deployment model of services architectures on the Internet that distinguishes between the roles of Service Developer, Service Provider and cloud Platform Provider.

The Service Developers design and develop software that the Service Providers put in operation as a service providing component on a cloud platform handled by a Platform Provider. Interoperability platform: technological platform allowing interoperability of systems whose implementations are a priori non-interoperable. Interoperability testing : activity of proving that end-to-end functionality between at least two communicating systems is as required by the base standard s on which those systems are based.

Loosely coupled systems : systems whose components have a minimum of interdependencies to prevent that changes in one component require adaptations in another component.

Middleware : software that mediates between applications and operating systems, consisting of a set of services that enable interoperability in support of distributed architectures by passing data between applications.

So, for example, the data in one database can be accessed through another database. Model-based testing : 1 testing based on a model of the component or system under test, e. Model Driven Architecture MDA : software development strategy in which requirements and specifications are represented through formal models at different levels of abstraction that are transformed to system implementations OMG.

Observation: test data reflecting the reactions from the SUT. Off-nominal testing : using test cases that are unlikely to be selected according to the usage-based model. Oracle : see test oracle. Pairwise testing : black box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters.

Platform as a Service PaaS : a cloud service model, in which cloud providers offer to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment.

Private cloud : a cloud deployment model where the infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers e. It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises.

Process virtual machine: a virtual machine designed to run a single program, which means that it supports a single process. Such virtual machines are usually closely suited to one or more programming languages and built with the purpose of providing program portability and flexibility amongst other things. Public cloud : a cloud deployment model where the infrastructure is provisioned for open use by the general public.

It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider.

Reliability: the ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations. Reliability testing : the process of testing to determine the reliability of a software product.

Security testing : a process to determine that an information system protects data and maintains functionality as intended. The six basic security concepts that need to be covered by security testing are: i confidentiality, ii integrity, iii authentication, iv availability, v authorization and vi non-repudiation.

Security testing is challenging the security related aspects of the application. Service application programming interface: an application programming interface implemented on an interoperability platform. Service choreography: exchange of messages in a services architecture for which an interaction protocol among participants is defined from a global perspective, each participant implementing its role without central control. Service choreography model: model of the exchange of messages in a services architecture for which an interaction protocol among participants is defined from a global perspective.

Service choreography testing: testing the control flow of a service component architecture against a service choreography model. Service component: a deployed software component implementing one or more service provider and consumer roles.

Service component architecture: software technology providing an implementable model for composing applications that follow Service-Oriented Architecture principles OASIS. Service composition : relationship among service components of a service component architecture in which, in order to provide services, service components consume services provided by other service components.

Service composition model: control and data flow model of a service composition that conforms to a formal meta-model. Service composition testing: testing a service composition against a service composition model.

Service contract: a specification of a service including: i the service operations; ii the service interfaces of the parties; iii the service parties external behaviours , including security and performance aspects. Service contract model: a model of a service contract conforming to a formal meta-model. Service model: a service contract model or a services architecture model.

Service orchestration: exchange of messages among service components in a service component architecture that is conducted orchestrated through the execution of an orchestration script by a service component playing the orchestrator role. Service orchestration script: script expressed in an interpretable language that conducts a service orchestration. Service oriented architecture SOA : a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.

SOA is an architectural paradigm for defining how people, organizations, and systems provide and use services to achieve results. Service Platform Independent Model: logical model, i. Service Platform Specific Model: implementable model of a service on a specific platform. Service unit testing: testing of a service node of a deployed services architecture.

If the service component is a service composition, it is tested as a whole. Services architecture : network whose nodes are abstract system classes participants and whose links are services.

INTRODUCTION TO MINERAL SCIENCES PUTNIS PDF

Glossary: Terms, Definitions, and Acronyms

.

CPKB KOSMETIK PDF

ISTQB Glossary - page 4

.

ISTORIA IEROGLIFICA DE DIMITRIE CANTEMIR PDF

ISTQB Glossary - page 4

.

Related Articles