py.test syntax error

[spencescu]

I am getting the errors below when trying to execute py.test. Also, are you guys not supplying a test file for the OWASP ruleset? Are we expected to write our own?
Thanks in advance!

$ py.test test/test_default.py --ruledir test/yaml
usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --ruledir test/yaml
inifile: None
rootdir: /Users/sherman/Fastly/ftw

[csjperon]

There is quick start documentation here:

https://github.com/fastly/ftw/blob/master/docs/basic_usage.md

If you want to run a test corpus specifically for the OWASP CRS, they can be found here:

https://github.com/SpiderLabs/owasp-modsecurity-crs/tree/update-contributing-v3.2/util/regression-tests

The CRS tests assume that you have the Modsecurity log, so you will need to adjust the configuration
(settings.ini) to match your environment. More documentation can be found in the README.md for the repository path linked above.

Hope this helps. Thanks!

[spencescu]

One last question: I don't want to test a local WAF - can I use this framework for it by just pointing to an IP address? Thank you!

…

On Fri, Mar 8, 2019 at 11:02 PM Christian S.J. Peron < ***@***.***> wrote: There is quick start documentation here: https://github.com/fastly/ftw/blob/master/docs/basic_usage.md If you want to run a test corpus specifically for the the OWASP CRS, they can be found here: https://github.com/SpiderLabs/owasp-modsecurity-crs/tree/update-contributing-v3.2/util/regression-tests The CRS tests assume that you have the Modsecurity log, so you will need to adjust the configuration (settings.ini) to match your environment. More documentation can be found in the README.md for the repository path linked above. Hope this helps. Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKDFsoD5Rrnoyycmyp5wP1MxIpCwW5gHks5vUs_zgaJpZM4bkCKb> .

[csjayp]

You can override the target using the --destaddr option on the command line. In some cases (like when going through a CDN) you will need to specify or override the Host: header too. If you use the docker image both options are supported:

See: https://github.com/fastly/ftw/blob/master/docs/Docker.md

However, otherwise you would need to add some code to whatever test harness you are using as done here:

https://github.com/fastly/ftw/blob/master/tools/build_journal.py#L36

(or change the actual testing corpus to reflect what you want to accomplish with respect to targets and Host: headers)

[P4l1ndr0m]

Having the same issue. Followed the readme and the installation via virtualenv and still getting a syntax error.

[bobrich]

Edit: This appears to be a version issue with py.test. I pulled the fork(?) in the CRS-Support repo (https://github.com/CRS-support/ftw) and after following the install directions there (which include virtualenv) also followed the update from this comment to get it working: coreruleset/ftw#38 (comment)

-- was --

Same issue here as well. Tried install and readme instructions from above link. Running on AWS Linux.

Here's a quick dump of my environment:

[ec2-user@ip-172-31-64-72 ~]$ cat test_rules.py
#!/usr/bin/python
#
from ftw import ruleset, testrunner, http, errors
import pytest

def test_default(ruleset, test, destaddr):
    '''
        Default test with no log [logger] obj.
    '''
    runner = testrunner.TestRunner()
    try:
        last_ua = http.HttpUA()
        for stage in test.stages:
            if destaddr is not None:
                stage.input.dest_addr = destaddr
            if stage.input.save_cookie:
                runner.run_stage(stage, http_ua=last_ua)
            else:
                runner.run_stage(stage, logger_obj=None, http_ua=None)
    except errors.TestError as e:
        e.args[1]['meta'] = ruleset.meta
        pytest.fail('Failure! Message -> {0}, Context -> {1}'.format(e.args[0],e.args[1]))

[ec2-user@ip-172-31-64-72 ~]$ cat rules.yml
---
  meta:
    author: "Zack"
    enabled: true
    name: "rules.yaml"
    description: "Description"
  tests:
    -
      test_title: 1234
      stages:
        -
          stage:
            input:
              method: "GET"
              port: 80
              headers:
                  User-Agent: "Foo"
                  Host: "localhost"
              protocol: "http"
              uri: "/"
            output:
              status: 200

[ec2-user@ip-172-31-64-72 ~]$ which py.test
/usr/local/bin/py.test

[ec2-user@ip-172-31-64-72 ~]$ py.test test_rules.py --rules=rules.yml
usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --rules=rules.yml
  inifile: None
  rootdir: /home/ec2-user

[ec2-user@ip-172-31-64-72 ~]$ py.test test_rules.py --rules rules.yml
usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --rules rules.yml
  inifile: None
  rootdir: /home/ec2-user

[ec2-user@ip-172-31-64-72 ~]$ py.test test_rules.py --ruledir .
usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --ruledir .
  inifile: None
  rootdir: /home/ec2-user

[ec2-user@ip-172-31-64-72 ~]$ py.test test_rules.py --ruledir=.
usage: py.test [options] [file_or_dir] [file_or_dir] [...]
py.test: error: unrecognized arguments: --ruledir=.
  inifile: None
  rootdir: /home/ec2-user

[ec2-user@ip-172-31-64-72 ~]$ ls -l
total 16
drwxrwxr-x 10 ec2-user ec2-user 4096 Jun 15 13:50 ftw
-rw-rw-r--  1 ec2-user ec2-user  456 Jun 15 13:58 rules.yml
-rw-rw-r--  1 ec2-user ec2-user  742 Jun 15 13:56 test_rules.py
drwxrwxr-x  7 ec2-user ec2-user 4096 Jun 15 13:34 waf_testbed

[dermarr]

try: python setup.py install