Support new molostart and molotov.json flows

[pdehaan]

Ref: http://molotov.readthedocs.io/en/latest/tutorial/

[pdehaan]

Here were my early steps:

$ virtualenv venv -p python3
$ source ./venv/bin/activate
$ pip install molotov
$ molotov --version
$ molostart  # this triggers "The Wizard"

$ cat molotov.json  # this is the generated "skeleton" molotov.json file

{
    "molotov": {
        "tests": {
            "big": {
                "duration": 60,
                "processes": 10,
                "scenario": "loadtest.py",
                "workers": 100
            },
            "small": {
                "duration": 60,
                "scenario": "loadtest.py"
            },
            "smoke": {
                "duration": 1,
                "scenario": "loadtest.py"
            }
        }
    }
}

This is actually a good overview of some molotov.json internals: http://molotov.readthedocs.io/en/latest/slave/?highlight=molotov.json

As demonstrated in example, there are also two global options you can use when running the tests:

• requirements: points to a Pip requirements file that will be installed prior to the test
• env: mapping containing environment variables that will be set prior to the test

{
    "molotov": {
        "env": {
            "SERVER_URL": "http://aserver.net"
        },
        "requirements": "requirements.txt",
        "tests": {
            ...
        }
    }
}

This would be useful for setting globals such as the loadtest server URL, but I'm not sure yet if we'd be able to do test-specific ENV variables (which I believe we'd need -- or else we could break out each scenario into it's own specific file).