Custom engine modes on remote server

Hi.

It would be nice if I could select a specific engine mode which the remote server should run under.

Example:
I have 1 engine mode for long running performance tests.
I have 1 remote server.

I would like the remote server to e.g. run impacted long running tests to spot issues early, but skip running such tests locally.

p.s. I find this to be a "nice to have feature" when using remote servers "heavily" but would probably prioritize it quite low d.s.

Hi,

The engine modes themselves all happen on the client-side, and they basically determine what ends up in the processing queue.

I think the solution you may be after here can be achieved using the Test filter configuration setting. You can define a custom filter that applies to your local machine (as this is global affecting all engine modes) that will stop it from executing the long running tests. Assuming this filter isn't assigned to the grid node, the node should be free to pick up these tests.

Or is the issue that you want this behaviour to be easily adjustable? (i.e. at the flick of a switch).


Cheers,

Remco

Yes that seems like an acceptable way of handling it. Will test it out later.

Remco wrote:Or is the issue that you want this behaviour to be easily adjustable? (i.e. at the flick of a switch).

No, not as of today at least :).

Thanks.