madshutterbug (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
madshutterbug) wrote2006-10-05 03:22 pm
madshutterbug) wrote2006-10-05 03:22 pm
Nursing Geekitude
Once again, following upgrade of Major Software Vendor's software at Hospital, we have a Test Environment. This is important as we learn what the upgrade will let us do, and how to implement little fixes to bugs... yes, bugs. Un-Documented Features. Uh Huh.
So, it's a good thing to have a Test Environment.
Having the flag that lets us know which environment we're logging into set to "Production"? Not so much.
However, we have two tests to help verify that we are actually in Test Environment. One is, open up the OR Scheduler; compare it to the same app for the same day in Production. Good clue. The second is, if it's Slow As Molasses in an Ice Age, you're in Test.
Yup.
So, it's a good thing to have a Test Environment.
Having the flag that lets us know which environment we're logging into set to "Production"? Not so much.
However, we have two tests to help verify that we are actually in Test Environment. One is, open up the OR Scheduler; compare it to the same app for the same day in Production. Good clue. The second is, if it's Slow As Molasses in an Ice Age, you're in Test.
Yup.
no subject
(no subject)
no subject
I am personally a strong advocate of a test environment... especially when rolling back is difficult or impossible in the event of a stow stopper found 2 minutes after the rollout was finished.
(no subject)