Hi. I checked the tests, but the test_configuration.py seemed just focused on either configuration from the command line or through a config file.
We're calling behave through another test framework, which makes it easier to configure by initialising Configuration directly.

I a not quite sure what your problem exactly is (except that I think you are mistaken).
Using the --verbose option on the command-line works as expected.
The default for verbose mode is false.

• Can you explain what the exact problem is that you are trying to solve !
• Explain what is not as you expected and what you expected instead !

Hi @jenisys,

The issue is when instantiating a Configuration object and passing it verbose as a keyword argument.

The following would not enable verbose mode.

config = Configuration(verbose=True)
assert run_behave(config) == os.EX_OK

despite verbose being in the Configuration definition.

class Configuration(object):
    def __init__(self, command_args=None, load_config=True, verbose=None, **kwargs):

If verbose is explicitly offered as an argument my expectation is that setting it to True would enable verbose logging.

I will think about it.
But note that the following parameter usage performs what you desire:

config = Configuration([“—verbose“])
assert config.verbose is True
assert run_behave(config) == os.EX_OK

And that's probably what we will use for now.
However, given that we're calling Configuration directly and the library offers a possibility to pass arguments directly, it's much nice to organize all options in a dictionary and then expand it when calling Configuration.

options = {
    "junit": True,
    "load_config": False,
    # ...
    "verbose": True,
}

config = Configuration([], tags=tags, paths=[tests_path()], stage="", **options)