Database Reference
In-Depth Information
Designed for testing
Meaning
Requirement
Valid (we are testing what we
are supposed to test)
Service / Component APIs can be easily exposed to any existing testing tool (JMeter,
SoapUI, LoadUI, and so on) and all the test operations generated with low efforts.
Standardized Con-
tract
Verifiable (we must be able
to recreate the results)
Test results, achieved in one environment (JIT, for instance) can be easily recreated in
any other environment in testing hierarchy. This means no surprises in production!
Autonomy, State-
fulness
Autonomy, State-
fulness, Loose
Coupling
Reliable (we will trust test
results)
Service with acceptable characteristics achieved initially must not be obscured by later
amendments/implementations breaking services, technical consistency.
Comprehendible (we must be
able to understand the res-
ults)
Test results, sometime together with test suites must be stored in a place where it can be
reached, accessed, comprehended by any concerned party and re-implemented if neces-
sary.
Discoverability
(Beware of Ab-
straction)
This simple exercise demonstrates that there's neither any need to invent new principles
out of wishes or abstract illities, nor to multiply unnecessary entities:
Entia non sunt multiplicanda praeter necessitatem
--Ockham
Principles here act as precise technical guidance. Elaborative lists of more than 50 items,
produced as a collective effort of several departments in some enterprises, usually leave
only one question: how are you supposed to enforce all of them? A principle is the direct
order, and it is only good if you can control its fulfillment.
For good measure, may we suggest that you repeat this exercise for the remaining nine re-
quirements in that list?
Search WWH ::
Custom Search