Re: How much testing required after CVTRPGSRC?

On Wed, 2015-11-04 at 15:14 +0000, Bob Cagle wrote:

So why doesn't JDE just do this themselves and make it official? If a two-man team can do this over a weekend, what's their excuse?

If an end user does it and it all goes wrong, a bollocking ensues, a few
days of pain, then (hopefully) back to business as usual.

If a software house does it, thousands of man hours are needed to test
everything to what ever level of internal/external audit compliance are
required to prove it works (especially with BS/EU standards compliance;
not sure what the US equivalents are, but by some of the posts i've seen
on here just getting something moved from test to production can be a
nightmare of forms and certification)...

then validation of the "install" then roll out to clients, then the
knock on effect of clients having internal/external (to house) bespoke
changes that need re-working into code that while the same (function
wise) can no longer be compared directly so need to be pre-converted
prior to comparison, then changed, then promoted from test to production
and/or a whole new set of tests for standards and audit compliance.

etc.

and finally if some quirk or gotcha is missed because of wildly
differing data at customers to what the software house used (and made
worse by bespoke changes)... ooops, all hell breaks lose!

Thanks
Bob

-----Original Message-----
From: Jon Paris

True - but given that the compiler has been available for over 21 years … well let’s just say that other than the documented differences (such as the aforementioned FREE op-code) there can be very few differences that have yet to be reported and fixed.

One simple example - entire JDE suite converted by one customer (two people) over a weekend. CVTRPGSRC threw up a couple of things that were easily remedied. They were fixed and a mass recompile submitted on Saturday. Sunday they resolved the couple of compile failures and tested. Monday the new version went into production. Zero problems reported.

You mileage may vary - and normally I’d want more testing than this but … compatibility was, and still is, a very high priority for the compiler team.