Cédric L. Charlier

This is indeed not natively supported and there is no straight-forward way to handle that case. I'll add this to the backlog.

As explained by @FuegoArtificial, your specific example is easy to handle and doesn't necessitate new features. Create a ```group``` then a ```setup```. In this ```setup``` add an attribute ```run-once``` set...

The answer is mostly a yes, somewhere we're trying to move to .Net Core with the branch 2.0. But we've really limited time at this moment to work on NBi.

Quick note for myself: only when loading an existing testSuite, not when creating a new one

NBi is not a commercial project but a community project. It means that contributors are providing most of the contributions to the code, to the documentation, to the blogs, to...

No, there is no solution for this (AFAIK).

It's not supported by NBi and AFAIK, it's not possible.

The general design guideline for NBi is to have in the test-suite itself all items that are independent of the environment (dev, test, qa ...) and in config files things...

I get the scenario, but for this case, won’t it be possible to define a variable at the top, retrieving the environment (with an override on the configuration file or...

I fear that letting users define variables in external files will create a nightmare to debug with some variables existing in some files and not on other files.