3 ms·

> We kept the last generation of hardware around to run the test/demo environment which was end-to-end connected via HL7 to all the other test environments. If

> We kept the last generation of hardware around to run the test/demo environment which was end-to-end connected via HL7 to all the other test environments. If I understand right (and I may not, both your description and the OP), this may violate the OP's prohibition I've quoted below. What do you think? > "Run an individual service in a shared stateful development environment running all the other services" doesn't count. A shared development environment will be unreliable as it diverges more and more from the real system. The OP seems to be awfully strict.

benlivengood 6y ago
"Run all the services that make up the system in an isolated development environment" was maintained in all the test environments. It'd be a moderate disaster to mix live patient/billing data between prod and test and so the test systems linked together with independent test/demo/prod HL7 gateways.
- jrochkind1 6y ago
  Right. If I understand it, it does seem to me to be an acceptable and reasonable solution, and I can't think of a better one. But isn't it the "shared stateful development environment" the OP is saying is unacceptable? Since every developer doesn't get their own "last generation of hardware"? But I may be misunderstanding the OP? I am not trying to critisize what you did; I am trying to understand and possibly critique the OP. The OP seems unrealistic to me, despite it's protestations that it really isn't; but I may be misunderstnading the OP.
  - benlivengood 6y ago
    Shared stateful development environment implies that "hard-to-test" things are not tested. In that sense, sure; we had one active directory, one physical network, one physical workstation to trigger commands, one office chair, no test version of me, etc. So if the OP's language is not careful then it could include things in "the development environment" that don't make sense.

benlivengood 6y ago

"Run all the services that make up the system in an isolated development environment" was maintained in all the test environments. It'd be a moderate disaster to mix live patient/billing data between prod and test and so the test systems linked together with independent test/demo/prod HL7 gateways.

jrochkind1 6y ago
Right. If I understand it, it does seem to me to be an acceptable and reasonable solution, and I can't think of a better one. But isn't it the "shared stateful development environment" the OP is saying is unacceptable? Since every developer doesn't get their own "last generation of hardware"? But I may be misunderstanding the OP? I am not trying to critisize what you did; I am trying to understand and possibly critique the OP. The OP seems unrealistic to me, despite it's protestations that it really isn't; but I may be misunderstnading the OP.
- benlivengood 6y ago
  Shared stateful development environment implies that "hard-to-test" things are not tested. In that sense, sure; we had one active directory, one physical network, one physical workstation to trigger commands, one office chair, no test version of me, etc. So if the OP's language is not careful then it could include things in "the development environment" that don't make sense.