Zack Allen

We should do YAML lints in a travis job for our test rules http://yamllint.readthedocs.io/en/latest/ . There are advantages to having a standardized corpus of yaml files using a linter, such...

Docker container

2

We should use a docker container for ftw so people can pull from Docker hub FTW and run tests against whatever they have

Per test author

1

Each rule author makes sense for whoever made the initial file, but rulefiles are starting to get large, as seen [here](https://github.com/SpiderLabs/OWASP-CRS-regressions/blob/master/tests/REQUEST-933-APPLICATION-ATTACK-PHP/933110.yaml) We should have a per test author as testing...

http://docs.pytest.org/en/latest/xdist.html http://stackoverflow.com/questions/29958823/pytest-run-each-test-as-a-mutlitprocessing-process Due to the size of the corpus we are building, itd be great to run py.test with multiple cores to speed up testing time

Proxy support

1

Add proxy support w/ Input directive for yaml files This should be available in the http library that we use for socket writes