delphi - How to identify what projects have been affected by a code change -

delphi - How to identify what projects have been affected by a code change -

i have big application manage consisting of of 3 or 4 executables , many 50 .dlls. many of source code files shared across many of projects.

the problem familiar 1 many of - if alter source code want able identify of binaries alter and, therefore, appropriate retest.

a simple approach compare file sizes. 80% acceptable solution, there @ to the lowest degree theoretical possibility of missing something. secondly, gives me little indication has changed; ideal form of study on can filter out irrelevant (e.g. dates/versions copyrights etc..)

on plus side :

all .dcus in row - mean built single folder the build controlled script (.bat)(easy, example, emit .obj files if helps) svn makes easy collect (two) revisions comparison

on minus side

there no policy include used units in projects; units included because on search path. just knowing changed unit used/compiled project not sufficient proof binary affected.

before begin writing code solve problem inquire panel suggestions might have how approach this.

the rules of stackoverflow forbid me inquire recommended software, if has positive experiences of continuous integration tools help - great

i open suggestion or observation relevant in context.

it seems me question boils downwards knowing units contained in various executables. since using search paths, hard work out ahead of time. robust way find out consult .map file compiler emits. contains list of units contained in executable.

once know units contained in each executable, need know whether or not has changed in units. info contained in revision command system. set , have info need.

of course, because source code unit has changed, might argue re-testing not needed. perhaps alter made version, or date in copyright label or such. asking much able inquire computer create such judgement. @ point need human step , take responsibility.

what odd though asking question @ all. seems me enormously risky effort partial testing. cannot understand why don't retest entire product.

delphi svn dependency-management delphi-5