Hi all!

I seem to recall a small discussion with Peter Hugosson-Miller at ESUG in Brest (walking to lunch :)) in which he told me a bit about the tests they used where he worked. IIRC a LOT of them were indeed "meta tests" that were testing properties of the source code itself (metrics, lints etc).

Peter, any more ideas in this direction you can share?

If coupled with "background execution" (or hey, in a forked image through OSProcess so we don't mess up the one we work in) and immediate feedback in browser tools this is "winner stuff".

regards, Göran

Reply via email to