AndrewWolford
MIS
Hi everyone,
I have what I hope is a quick question around JD Edwards and testing within test environments. I have a client that says they maintain two DB/2 databases, one test, and one production. For testing, they say they 'detatch' their production objects and custom libraries and 'point' the objects/libraries to the test database. Basically they say they have 1 set of objects and libraries, with 2 databases. Is this possible to do?
I've always recommended/heard that you maintain 2 seperate environements, test and production. You migrate your production custom libraries and objects to the test/dev environment, do your new dev work, test on the test database, them promote your code to prodcution.
You can't just 'point' to the test database, make your changes and test, then point your objects back to the production database. Is this correct?
Thanks!
Andrew
I have what I hope is a quick question around JD Edwards and testing within test environments. I have a client that says they maintain two DB/2 databases, one test, and one production. For testing, they say they 'detatch' their production objects and custom libraries and 'point' the objects/libraries to the test database. Basically they say they have 1 set of objects and libraries, with 2 databases. Is this possible to do?
I've always recommended/heard that you maintain 2 seperate environements, test and production. You migrate your production custom libraries and objects to the test/dev environment, do your new dev work, test on the test database, them promote your code to prodcution.
You can't just 'point' to the test database, make your changes and test, then point your objects back to the production database. Is this correct?
Thanks!
Andrew