Blacklist for tests or test directories for different environments.

[ozymandias547]

We have over 10 different servers/environments to run our tests on. Not all tests can be run on all servers, and we'd like to be able to configure more specifically which tests can't be run in the settings.json without changing the command lines for each build environment. I propose we add a blacklist where we can specify tests or test directories to skip within the settings.json, one for each environment.

I'm proposing the config to be like so:

"test_settings" : {
    "default" : {
        ...
        "blacklist" : {
              "files" : ["widgets/file1"],
              "directories" : ["pages", "templates"]
        },
    "env2" : {
        ...
        "blacklist" : {
              "files" : ["widgets/file3"],
              "directories" : ["pages", "registration"]
        }
    }
}

Thoughts?

[beatfactor]

I think it would be more elegant if we can overwrite the src_folders inside a specific test_settings section. How do you feel about this idea? I'm not sure about the term 'blacklist'...

[ozymandias547]

Moving this conversation to #110 pull request. We can talk about semantics or other ideas there.