We are in the process of upgrading from 9.8 to 12 in our test environment and I am hoping to fully test the new version before pushing it out to the masses. I have superusers scheduled to assit me in fully vetting the system but I am in need of test scenarios or a test check list to provide to each member of my testing team to make sure we test all the different parts and pieces and to track any issues.
Is anyone willing to share their test plans/scenarios? How do other offices test prior to releasing upgrades for general use?
I'd rather not spend hours re-creating a wheel we are all using....
Thanks!
Sonya
[email protected]
We would be interested in this as well. Thanks!
Betsy
I have a full test environment complete with a DTS.
Basically, we have a small copy of our DB loaded on the server.
- Jboss-test seperate (8 GB of RAM, dual quad)
- SQL 2008 R 2
- CPS-Test (DB copy, 32 GB of RAM, dual quad)
It runs a little slow because of the resources but it was the most we could throw at it. I use this environment to:
- test KB updates
- test client updates
- test SQL scripts
- test HL7 files coming in and being sent out
- Used it as a testing ground for new forms.
- chart access
- scheduling templates
The best part is when the client on test matches the version in production, so then users can just use the "test url" to connect to the test client. I also limit access to my best users (managers) only. Then they conduct trainings.
I have also trained my staff by completely nuking the DB and making them restore a backup, rebuild the website, and get the client going again.
Things you should watch out for post production updates (if they apply):
- Escript (should have its own server, via kryptiq)
- DTS (if test was fine this should be as well...but good to be careful)
- JBOSS (if this is dead you can't login)
- Patient portal (we use kryptiq)
- Document Management (also through kryptiq)
- CQR portal access (for MU)
The third party stuff will have minimum version requirements for CPS 10, 11, 12 etcetera. I don't have a robust enough environment to make a test box for ALL my apps, so i usually schedule calls to talk with engineers before an update, and perform the third party updates weeks before to make sure i'm in the clear.
That's great, thanks!
I would be interested in this as well. Thank you