Add support for Profiles to modify behaviour for different environments about chorus HOT 4 CLOSED

It's an interesting requirement and also interesting that you're using Chorus in a virtualized environment. We're thinking about some sort of integration with Docker and/or other virtualization technologies since it seems a logical next step.

To meet your requirement it sounds as if it might be a good idea to introduce some sort of concept of profiles here. i.e. you'd have a local profile for developers (which starts processes locally) and a profile for your virtualized integration testing environment in which the processes are not started. When running the interpreter you'd specify the profile as a parameter. Perhaps we could add profile as a new parameter to a process config, such that a process only starts when chorus is running in a profile which matches the config setting. Would that be a good solution?

The concept of a profile might be useful to other handlers as well, both built in and custom. We could add the profile as an injectable property using @ChorusResource so that handler classes can be made aware of the current profile.

You could also do this more in the manner you describe above, by writing a custom processes handler class. In the latest Chorus 1.6.x the process management has been devolved to a subsystem called ProcessManager, and the processes handler is nothing more than a lightweight wrapper which contains the step definitions and calls into the manager to stop/start processes. One advantage in this is that you can very easily control processes from your own handlers, or write handler steps of your own which interact with the new ProcessManager to start/stop processes etc. If you wanted to do things exactly as detailed above, the best way at present would be to write a handler of your own with a step which applies the extra logic, and calls the ProcessManager to start the process. You'll need to wait for 1.6.10, in your case, which should be released very soon. It may change a little for 2.0.x in the pipeline so you may have to rework whatever you write slightly for that major release.

from chorus.

I like the profiles idea as well.
It will be useful.

I'll wait for 1.6.10 in the mean time.

We are using ansible/vagrant/chorus/vsphere for our VM testing

from chorus.

We'll try to add it for 2.0.x

from chorus.

This is done for config variables

We will shortly add support for extra .profile files which can contain scenarios to help set up or tear down the test environment for a specific profile

from chorus.