I suggest you ...

Remote server: Conditionally run tests depending on which remote server they are running on.

Scenario:
I have http integration tests which will report results in one way locally (due to IIS custom errors) and one way remotely. Thus for tests verifying the corretc "remote" response I would like them to run on a grid node that is not running on my local machine.

The current "Capabilities" is not attractive since that is set on grid node server itself and requires project-specific user configurations on each grid node server (which annoys the developers if they are running them on their dev machines if I will need to interrupt to tweak custom project settings).

Possible solutions I can think of:
* An option to customize engine mode to filter on e.g. grid node server name (includes tests conditionally depending on if that server name is connected), e.g. "... or (test name like *httpIntegration* and gride node name is (server1 or server2))".
* Be able to set "capabilities" as part of my local configuration of the grid server (the "NCrunch Distributed Processing" window), not affecting the global grid node server for other users.
* Be able to set custom environment variables per server via "NCrunch Distributed Processing" window.

2 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

GreenMoose shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • GreenMoose commented  ·   ·  Flag as inappropriate

    >* Be able to set custom environment variables per server via "NCrunch Distributed Processing" window.
    Not sure what I was thinking of here. I can't really see how this would help (other than conditionally marking tests as inconclusive but that isn't the behavior I'm after).

Feedback and Knowledge Base