Forwarding this question to the release-team mailing list because Roman isn’t a member of that list (and I’m not an admin of it, so I can’t approve his post). Nomi Begin forwarded message:

From: Roman Sutormin <[email protected]> Date: Mon, Mar 10, 2014 at 2:11 PM Subject: Question about testing environment To: [email protected] Cc: Adam Arkin <[email protected]>

Hello everybody,

I have little bit strange question. Why don't we make testing environment for tests in our projects?

My problem is that now I need to install local workspace service (and shock server + mongo that are used in WS) and job status service in order to be able to run tests for my service (genome comparison). But I'm sure that everybody who is developing services would be glad to have testing services and dbs that are necessary for running tests without installing all necessary parts on some random magellan instances or even locally.

Another useful outcome of testing env will be ability to install automation testing software like https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test .

Thanks for your ideas and suggestions.

-Roman.