27.07.2013 Views

ISTQB begreber på dansk (2012) - Danish Software Testing Board

ISTQB begreber på dansk (2012) - Danish Software Testing Board

ISTQB begreber på dansk (2012) - Danish Software Testing Board

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

klassifikationstræmetode En black-box testdesignteknik hvor testcases, beskrevet vha.et classification tree method A black box test design technique in which test cases,<br />

klassifikationstræ, designes til at eksekvere kombinationer af<br />

described by means of a classification tree, are designed to<br />

input- og/eller outputdomæner. [Grochtmann]<br />

execute combinations of representatives of input and/or output<br />

domains. [Grochtmann]<br />

kode Computer-instruktioner og datadefinitioner udtrykt i et<br />

programmeringssprog eller i et format genereret af en<br />

assembler, compiler eller anden oversætter. [IEEE 610]<br />

code Computer instructions and data definitions expressed in a<br />

programming language or in a form output by an assembler,<br />

compiler or other translator. [IEEE 610]<br />

kodeanalysator Se statisk kodeanalysator. code analyzer See static code analyzer.<br />

kodebaseret test Se white-box test. code-based testing See white box testing.<br />

kodedækning En analysemetode til afgørelse af hvilke dele af softwaren, der code coverage An analysis method that determines which parts of the<br />

er blevet eksekveret (dækket) af en testsuite og hvilke dele,<br />

software have been executed (covered) by the test suite and<br />

der ikke er blevet eksekveret, for eksempel instruktiondækning,<br />

which parts have not been executed, e.g. statement coverage,<br />

beslutningsdækning eller betingelsesdækning.<br />

decision coverage or condition coverage.<br />

kollegareview Et review af et softwarearbejdsprodukt foretaget af<br />

ophavsmandens kolleger for at identificere defekter (fejl) og<br />

forbedringer. Eksempler er inspektion, teknisk review og<br />

walkthrough.<br />

kombinatorisk test En måde til at identificere en passende delmængde af<br />

testkombinationer for at opnå et forudbestemt niveau af<br />

dækning, når der testes et objekt med flere parametre, og hvor<br />

disse parametre hver især har flere værdier, hvilket giver<br />

anledning til flere kombinationer end det er muligt at teste<br />

inden for den afsatte tid. Se også klassifikationstræmetode,<br />

parvis test, ortogonal tabeltest.<br />

kommerciel<br />

hyldesoftware<br />

peer review A review of a software work product by collegues of the<br />

producer of the product for the purpose of identifying defects<br />

and improvements. Examples are inspection, technical review<br />

and walkthrough.<br />

combinatorial testing A means to identify a suitable subset of test combinations to<br />

achieve a predetermined level of coverage when testing an<br />

object with multiple parameters and where those parameters<br />

themselves each have several values, which gives rise to more<br />

combinations than are feasible to test in the time allowed. See<br />

also classification tree method, pairwise testing, orthogonal<br />

Se hyldesoftware. Commercial Off-The-Shelf<br />

software<br />

array testing.<br />

See off-the-shelf software. F<br />

kompatibilitetstest Se tværoperationalitetstest. compatibility testing See interoperability testing.<br />

kompleksitet Den grad hvortil en komponent eller system har et design complexity The degree to which a component or system has a design F<br />

og/eller intern struktur, der er vanskelig at forstå, vedligeholde<br />

and/or internal structure that is difficult to understand, maintain<br />

og verificere. Se også cyklomatisk kompleksitet.<br />

and verify. See also cyclomatic complexity.<br />

komplet test Se udtømmende test. complete testing See exhaustive testing.<br />

komponent Det mindste softwareelement der kan testes i isolation. component A minimal software item that can be tested in isolation.<br />

komponentintegrationste Se komponentintegrationstest (2). integration testing in the See component integration testing.<br />

st (1)<br />

small<br />

komponentintegrationste Test udført for at afsløre defekter i grænseflader (snitflader) og component integration <strong>Testing</strong> performed to expose defects in the interfaces and<br />

st (2)<br />

samspil mellem integrerede komponenter.<br />

testing<br />

interaction between integrated components.<br />

komponentspecifikation En beskrivelse af en komponents funktion i form af dens component specification A description of a component’s function in terms of its output<br />

outputværdier for specifikke inputværdier under specifikke<br />

values for specified input values under specified conditions,<br />

forhåndsbetingelser, og krævede ikke-funktionel adfærd (for<br />

eksempel resurseforbrug).<br />

and required non-functional behavior (e.g. resource-utilization).<br />

komponenttest Test af individuelle softwarekomponenter. [Efter IEEE 610] component testing The testing of individual software components. [After IEEE 610] F<br />

konfiguration Sammensætningen af en komponent eller et system defineret<br />

ud fra antallet, typen og sammenkoblingerne imellem dets<br />

enkeltdele.<br />

konfigurationselement En sammensætning af hardware, software eller begge, der er<br />

udpeget til konfigurationsstyring og behandlet som en enkelt<br />

enhed i konfigurationsstyringsprocessen. [IEEE 610]<br />

configuration The composition of a component or system as defined by the<br />

number, nature, and interconnections of its constituent parts.<br />

configuration item An aggregation of hardware, software or both, that is<br />

designated for configuration management and treated as a<br />

single entity in the configuration management process. [IEEE<br />

610]<br />

ATA<br />

F<br />

F<br />

ATA

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!