I do not know if the VETO or VEST patterns are mentioned any list of software testing heuristics.
VEST Verify, Enrich, Standardise, Transform
- variant of the VETO architecture pattern
- can be used independently for extract and load processes
- can be a useful heuristic for thinking about tests for data transfer processes.
The VERIFY and TRANSFORM components are usually pretty obvious.
Consideration of ENRICH and STANDARDISE components can sometimes uncover less obvious and more subtle issues.
ENRICH (often a special kind of transform)
- convert local lookup code or primary key to a physical unit symbol
- ex - 143 > metres
STANDARDISE (often a special kind of transform)
- datetime: BST > GMT?
- datetime: EST > GMT?
Any conversion to a local standard physical unit could be thought of as part of the S from VEST.
(Incorrect assumptions about physical units resulted in an expensive spacecraft burning up in the atmosphere of Mars some years ago.)
I came across this pattern at a commodities trading company where it was used to design a systems integration toolkit. It became natural for the test team to think in terms of the pattern when creating tests.