| podobné slovo | definícia |
aboveground nuclear testing
(encz) | aboveground nuclear testing,nadzemní nukleární testování |
hypothesis testing
(encz) | hypothesis testing, |
means-testing
(encz) | means-testing, |
mental testing
(encz) | mental testing, n: |
protesting
(encz) | protesting,protestování n: Zdeněk Brožprotesting,protestující adj: Zdeněk Brož |
protestingly
(encz) | protestingly, |
quality testing
(encz) | quality testing,zkoušení jakosti Pavel Cvrček |
sign of testing
(encz) | sign of testing,zkušební značka Pavel Cvrček |
testing
(encz) | testing,testování n: Zdeněk Brožtesting,zkoušení Jakub Kolčář |
testing ground
(encz) | testing ground, n: |
testing room
(encz) | testing room, n: testing room,zkušebna n: Zdeněk Brož |
unprotesting
(encz) | unprotesting, adj: |
x-ray testing
(encz) | x-ray testing,rentgenová kontrola n: [tech.] mammx-ray testing,rentgenování v: [tech.] mamm |
Attesting
(gcide) | Attest \At"test"\, v. t. [imp. & p. p. Attested; p. pr. & vb.
n. Attesting.] [L. attestari; ad + testari to bear witness:
cf. F. attester.]
1. To bear witness to; to certify; to affirm to be true or
genuine; as, to attest the truth of a writing, a copy of
record.
[1913 Webster]
Facts . . . attested by particular pagan authors.
--Addison.
[1913 Webster]
2. To give proof of; to manifest; as, the ruins of Palmyra
attest its ancient magnificence.
[1913 Webster]
3. To call to witness; to invoke. [Archaic]
[1913 Webster]
The sacred streams which Heaven's imperial state
Attests in oaths, and fears to violate. --Dryden.
[1913 Webster] |
Contesting
(gcide) | Contest \Con*test"\, v. t. [imp. & p. p. Contested; p. pr. &
vb. n. Contesting.] [F. contester, fr. L. contestari to
call to witness, contestari litem to introduce a lawsuit by
calling witnesses, to bring an action; con- + testari to be a
witness, testic witness. See Testify.]
1. To make a subject of dispute, contention, litigation, or
emulation; to contend for; to call in question; to
controvert; to oppose; to dispute.
[1913 Webster]
The people . . . contested not what was done.
--Locke.
[1913 Webster]
Few philosophical aphorisms have been more frequenty
repeated, few more contested than this. --J. D.
Morell.
[1913 Webster]
2. To strive earnestly to hold or maintain; to struggle to
defend; as, the troops contested every inch of ground.
[1913 Webster]
3. (Law) To make a subject of litigation; to defend, as a
suit; to dispute or resist; as a claim, by course of law;
to controvert.
[1913 Webster]
To contest an election. (Polit.)
(a) To strive to be elected.
(b) To dispute the declared result of an election.
Syn: To dispute; controvert; debate; litigate; oppose; argue;
contend.
[1913 Webster] |
Contestingly
(gcide) | Contestingly \Con*test"ing*ly\, adv.
In a contending manner.
[1913 Webster] |
Detesting
(gcide) | Detest \De*test"\, v. t. [imp. & p. p. Detested; p. pr. & vb.
n. Detesting.] [L. detestare, detestatum, and detestari, to
curse while calling a deity to witness, to execrate, detest;
de + testari to be a witness, testify, testis a witness: cf.
F. d['e]tester. See Testify.]
1. To witness against; to denounce; to condemn. [Obs.]
[1913 Webster]
The heresy of Nestorius . . . was detested in the
Eastern churches. --Fuller.
[1913 Webster]
God hath detested them with his own mouth. --Bale.
[1913 Webster]
2. To hate intensely; to abhor; to abominate; to loathe; as,
we detest what is contemptible or evil.
[1913 Webster]
Who dares think one thing, and another tell,
My heart detests him as the gates of hell. --Pope.
Syn: To abhor; abominate; execrate. See Hate.
[1913 Webster] |
Obtesting
(gcide) | Obtest \Ob*test"\, v. t. [imp. & p. p. Obtested; p. pr. & vb.
n. Obtesting.] [L. obtestari; ob (see Ob-) + testari to
witness, fr. testis a witness.]
1. To call to witness; to invoke as a witness. [R.] --Dryden.
[1913 Webster]
2. To beseech; to supplicate; to beg for. [R.]
[1913 Webster] |
Protesting
(gcide) | Protest \Pro*test"\, v. i. [imp. & p. p. Protested; p. pr. &
vb. n. Protesting.] [F. protester, L. protestari, pro
before + testari to be a witness, testis a witness. See
Testify.]
1. To affirm in a public or formal manner; to bear witness;
to declare solemnly; to avow.
[1913 Webster]
He protest that his measures are pacific. --Landor.
[1913 Webster]
The lady doth protest too much, methinks. --Shak.
[1913 Webster]
2. To make a solemn declaration (often a written one)
expressive of opposition; -- with against; as, he protest
against your votes. --Denham.
[1913 Webster]
The conscience has power . . . to protest againts
the exorbitancies of the passions. --Shak.
[1913 Webster]
Syn: To affirm; asseverate; assert; aver; attest; testify;
declare; profess. See Affirm.
[1913 Webster] |
Protestingly
(gcide) | Protestingly \Pro*test"ing*ly\, adv.
By way of protesting.
[1913 Webster] |
protestingprenominal protestant
(gcide) | complaining \complaining\ (k[o^]m*pl[=a]n"[i^]mg) adj.
uttering complaints. Opposite of uncomplaining.
[prenominal]
Note: [Narrower terms: faultfinding, grumbling(prenominal):
{fretful, querulous, whiney, whining(prenominal),
whiny}; protesting(prenominal), protestant]
Syn: complaintive.
[WordNet 1.5] |
Testing machine
(gcide) | Testing \Test"ing\, n.
1. The act of testing or proving; trial; proof.
[1913 Webster]
2. (Metal.) The operation of refining gold or silver in a
test, or cupel; cupellation.
[1913 Webster]
Testing machine (Engin.), a machine used in the
determination of the strength of materials, as iron,
stone, etc., and their behavior under strains of various
kinds, as elongation, bending, crushing, etc.
[1913 Webster] |
Undetesting
(gcide) | Undetesting \Undetesting\
See detesting. |
mental testing
(wn) | mental testing
n 1: any standardized procedure for measuring sensitivity or
memory or intelligence or aptitude or personality etc; "the
test was standardized on a large sample of students" [syn:
test, mental test, mental testing, {psychometric
test}] |
testing
(wn) | testing
n 1: the act of subjecting to experimental test in order to
determine how well something works; "they agreed to end the
testing of atomic weapons"
2: an examination of the characteristics of something; "there
are laboratories for commercial testing"; "it involved
testing thousands of children for smallpox"
3: the act of giving students or candidates a test (as by
questions) to determine what they know or have learned [syn:
examination, testing] |
testing ground
(wn) | testing ground
n 1: a region resembling a laboratory inasmuch as it offers
opportunities for observation and practice and
experimentation; "the new nation is a testing ground for
socioeconomic theories"; "Pakistan is a laboratory for
studying the use of American troops to combat terrorism"
[syn: testing ground, laboratory] |
testing room
(wn) | testing room
n 1: a room in which tests are conducted [syn: test room,
testing room] |
acceptance testing
(foldoc) | acceptance testing
Formal testing conducted to determine whether a
system satisfies its acceptance criteria and thus whether the
customer should accept the system.
(1996-05-10)
|
alpha testing
(foldoc) | alpha testing
Testing of software at the developer's site by
the customer. The stage before beta testing.
(1996-05-10)
|
application testing
(foldoc) | system testing
application testing
(Or "application testing") A type of testing to
confirm that all code modules work as specified, and that the
system as a whole performs adequately on the platform on
which it will be deployed.
System testing should be performed by testers who are trained
to plan, execute, and report on application and system code.
They should be aware of scenarios that might not occur to the
end user, like testing for null, negative, and format
inconsistent values. A tester should be able to repeat the
steps that caused an error.
(2003-09-24)
|
automated testing
(foldoc) | automated testing
Software testing assisted with software tools
that require no operator input, analysis, or evaluation.
(2001-05-20)
|
beta testing
(foldoc) | beta testing
beta test
beta version
Evaluation of a pre-release (potentially unreliable)
version of a piece of software (or possibly hardware) by
making it available to selected users ("beta testers") before it
goes on general distribution.
Beta testign aims to discover bugs that only occur in certain
environments or under certain patterns of use, while reducing the
volume of feedback to a manageable level. The testers benefit by
having earlier access to new products, features and fixes.
Beta testing may be preceded by "alpha testing", performed
in-house by a handful of users (e.g. other developers or friends),
who can be expected to give rapid, high quality feedback on design
and usability. Once the product is considered to be usable for
its intended purpose it then moves on to "beta testing" by a
larger, but typically still limited, number of ordinary users, who
may include external customers.
Some companies such as Google or {Degree Jungle
(http://www.degreejungle.com/rankings/best-online-colleges)}
stretch the definition, claiming their products are "in beta" for
many months by millions of users.
The term derives from early 1960s terminology for product cycle
checkpoints, first used at IBM but later standard throughout the
industry. "Alpha test" was the unit test, module test or
component test phase; "Beta Test" was initial system test.
These themselves came from earlier A- and B-tests for hardware.
The A-test was a feasibility and manufacturability evaluation done
before any commitment to design and development. The B-test was a
demonstration that the engineering model functioned as specified.
The C-test (corresponding to today's beta) was the B-test
performed on early samples of the production design.
(2013-06-09)
|
black-box testing
(foldoc) | functional testing
black-box testing
closed-box testing
(Or "black-box testing", "closed-box testing") The
application of test data derived from functional requirements
without regard to how the system is implemented.
(1996-05-15)
|
bottom-up testing
(foldoc) | bottom-up testing
An integration testing technique that tests the
low-level components first using test drivers for those
components that have not yet been developed to call the
low-level components for test.
Compare bottom-up implementation.
(1996-05-10)
|
branch coverage testing
(foldoc) | branch coverage testing
A test method which aims to ensure that each
possible branch from each decision point (e.g. "if" statement)
is executed at least once, thus ensuring that all reachable
code is executed.
(1996-05-10)
|
clear box testing
(foldoc) | white box testing
clear box testing
glass box testing
open box testing
(Or "clear", "glass", "open") Software testing
approaches that examine the program structure and derive test
data from the program logic.
Structural testing is sometimes referred to as clear-box
testing since white boxes are considered opaque and do not
really permit visibility into the code.
(1996-05-10)
|
closed-box testing
(foldoc) | functional testing
black-box testing
closed-box testing
(Or "black-box testing", "closed-box testing") The
application of test data derived from functional requirements
without regard to how the system is implemented.
(1996-05-15)
|
computer-aided software testing
(foldoc) | Computer-Aided Software Testing
(CAST) Automated software testing in one or more
phases of the software life-cycle.
(1996-05-10)
|
error-based testing
(foldoc) | error-based testing
Testing where information about programming
style, error-prone language constructs, and other programming
knowledge is applied to select test data capable of detecting
faults, either a specified class of faults or all possible
faults.
(1996-05-13)
|
exhaustive testing
(foldoc) | exhaustive testing
Executing a program with all possible
combinations of inputs or values for program variables.
(1996-05-13)
|
failure-directed testing
(foldoc) | failure-directed testing
heuristics testing
(Or "heuristics testing") Software testing based
on the knowledge of the types of errors made in the past
that are likely for the system under test.
(1996-05-16)
|
fault-based testing
(foldoc) | fault-based testing
Software testing using test data designed to
demonstrate the absence of a set of pre-specified faults;
typically, frequently occurring faults. For example, to
demonstrate that the software handles or avoids {divide by
zero} correctly, the test data would include zero.
(1996-05-15)
|
functional testing
(foldoc) | functional testing
black-box testing
closed-box testing
(Or "black-box testing", "closed-box testing") The
application of test data derived from functional requirements
without regard to how the system is implemented.
(1996-05-15)
|
future date testing
(foldoc) | future date testing
The process of setting a computer's date to a future
date to test a program's (expected or unexpected) date
sensitivity. Future date testing only shows the effects of
dates on the computer(s) under scrutiny, it does not take into
account knock-on effects of dates on other connected systems.
(2000-09-11)
|
glass box testing
(foldoc) | white box testing
clear box testing
glass box testing
open box testing
(Or "clear", "glass", "open") Software testing
approaches that examine the program structure and derive test
data from the program logic.
Structural testing is sometimes referred to as clear-box
testing since white boxes are considered opaque and do not
really permit visibility into the code.
(1996-05-10)
|
heuristics testing
(foldoc) | failure-directed testing
heuristics testing
(Or "heuristics testing") Software testing based
on the knowledge of the types of errors made in the past
that are likely for the system under test.
(1996-05-16)
|
hybrid testing
(foldoc) | hybrid testing
A combination of top-down testing with {bottom-up
testing} of prioritised or available components.
(1996-05-22)
|
integration testing
(foldoc) | integration testing
A type of testing in which software and/or
hardware components are combined and tested to confirm that
they interact according to their requirements. Integration
testing can continue progressively until the entire system has
been integrated.
(2003-09-24)
|
intrusive testing
(foldoc) | Intrusive Testing
Testing that collects timing and processing
information during program execution that may change the
behaviour of the software from its behavior in a real
environment. Intrusive testing usually involves additional
code embedded in the software being tested or additional
processes running concurrently with software being tested on
the same processor.
(1996-12-01)
|
manual testing
(foldoc) | manual testing
That part of software testing that requires human
input, analysis, or evaluation.
(1996-12-27)
|
mutation testing
(foldoc) | Mutation Testing
A method to determine test set thoroughness by
measuring the extent to which a test set can discriminate the
program from slight variants of the program.
(1996-12-27)
|
nonintrusive testing
(foldoc) | nonintrusive testing
Testing that is transparent to the software under
test, i.e., does not change its timing or processing
characteristics. Nonintrusive testing usually involves
additional hardware that collects timing or processing
information and processes that information on another
platform.
|
open box testing
(foldoc) | white box testing
clear box testing
glass box testing
open box testing
(Or "clear", "glass", "open") Software testing
approaches that examine the program structure and derive test
data from the program logic.
Structural testing is sometimes referred to as clear-box
testing since white boxes are considered opaque and do not
really permit visibility into the code.
(1996-05-10)
|
operational testing
(foldoc) | operational testing
A US DoD term for testing performed by the
end-user on software in its normal operating environment.
(1997-01-07)
|
outside-in testing
(foldoc) | outside-in testing
A strategy for integration testing where units
handling program inputs and outputs are tested first, and
units that process the inputs to produce output are
incrementally included as the system is integrated. A form of
hybrid testing.
(1997-01-07)
|
path coverage testing
(foldoc) | path coverage testing
Testing a program by examining which lines of
executable code are visited (as in code coverage testing)
and also the ways of getting to each line of code and the
subsequent sequence of execution.
Path coverage testing is the most comprehensive type of
testing that a test suite can provide. It can find more
bugs, especially those that are caused by data coupling.
However, path coverage is hard and usually only used for small
and/or critical sections of code.
(2005-01-25)
|
random testing
(foldoc) | random testing
A black-box testing approach in which
software is tested by choosing an arbitrary subset of all
possible input values. Random testing helps to avoid the
problem of only testing what you know will work.
(2001-04-30)
|
regression testing
(foldoc) | regression testing
Part of the test phase of software development
where, as new modules are integrated into the system and the
added functionality is tested, previously tested functionality
is re-tested to assure that no new module has corrupted the
system.
[Bennatan, E.M., "Software Project Management", 2nd edition,
McGraw-Hill International, 1992].
(1995-12-04)
|
risk based testing
(foldoc) | Risk Based Testing
Testing based on identification of potential risks
(or "candidate risks"), which should be analysed by the
project stakeholder or which might appear during the project's
development.
(2006-09-07)
|
stress testing
(foldoc) | stress testing
Testing aimed at investigating the behaviour of a
software or hardware equipment in out of ordinary operating
conditions.
(1998-03-27)
|
system testing
(foldoc) | system testing
application testing
(Or "application testing") A type of testing to
confirm that all code modules work as specified, and that the
system as a whole performs adequately on the platform on
which it will be deployed.
System testing should be performed by testers who are trained
to plan, execute, and report on application and system code.
They should be aware of scenarios that might not occur to the
end user, like testing for null, negative, and format
inconsistent values. A tester should be able to repeat the
steps that caused an error.
(2003-09-24)
|
testing
(foldoc) | test
testing
The process of exercising a product to identify
differences between expected and actual behaviour. Typically
testing is bottom-up: unit testing and integration testing
by developers, system testing by testers, and {user
acceptance testing} by users.
Test coverage attempts to assess how complete a test has
been.
2. The second stage in a generate and test search
algorithm.
[Jargon File]
(2003-09-24)
|
unit testing
(foldoc) | unit testing
The type of testing where a developer (usually the
one who wrote the code) proves that a code module (the "unit")
meets its requirements.
(2003-09-24)
|
user acceptance testing
(foldoc) | user acceptance testing
The type of testing where monitored users
determine whether a system meets all their requirements, and
will support the business for which it was designed.
(2003-09-24)
|
white box testing
(foldoc) | white box testing
clear box testing
glass box testing
open box testing
(Or "clear", "glass", "open") Software testing
approaches that examine the program structure and derive test
data from the program logic.
Structural testing is sometimes referred to as clear-box
testing since white boxes are considered opaque and do not
really permit visibility into the code.
(1996-05-10)
|
ATTESTING WITNESS
(bouvier) | ATTESTING WITNESS. One who, upon being required by the parties to an
instrument, signs his name to it to prove it, and for the purpose of
identification.
2. The witness must be desired by the parties to attest it, for unless
this be done, he will not be an attesting witness, although he may have seen
the parties execute it. 3 Campb. 232. See Competent witness; Credible
witness; Disinterested witness; Respectable witness; Subscribing witness;
and Witness; Witness instrumentary; 5 Watts, 399; 3 Bin. 194.
|