Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to test a server with docker ? #106

Open
jonadem opened this issue Jun 3, 2020 · 1 comment
Open

How to test a server with docker ? #106

jonadem opened this issue Jun 3, 2020 · 1 comment

Comments

@jonadem
Copy link
Contributor

jonadem commented Jun 3, 2020

I tried unluckily:
$ sudo docker run -it --rm -v "${PWD}/config:/config" -v "${PWD}/reports:/reports" --name fuzzingclient crossbario/autobahn-testsuite
And I get :

Using explicit spec file '/config/fuzzingserver.json'
Loading spec from /config/fuzzingserver.json
Traceback (most recent call last):
File "/usr/local/bin/wstest", line 11, in <module>
    sys.exit(run())
File "/usr/local/site-packages/autobahntestsuite/wstest.py", line 337, in run
    spec = json.loads(open(spec_filename).read())
IOError: [Errno 2] No such file or directory: '/config/fuzzingserver.json'`

In config/, I have a fuzzingclient.jsonfrom there. If I put a fuzzingserver.json, it behave like it is testing for clients, which is not why I am looking for.

How can I test a websocket server ?

@skaarj1989
Copy link

I'm testing my server implementation with:

docker run -it --rm -v %cd%\config:/config -v %cd%\reports:/reports crossbario/autobahn-testsuite wstest -m fuzzingclient -s /config/fuzzingclient.json

It's Windows, so change %cd% to ${PWD}

fuzzingclient.json

{
  "options": {},
  "outdir": "./reports/servers",
  "servers": [
    {
      "agent": "AVR / W5100 / Ethernet",
      "url": "ws://192.168.46.180:9001"
    }
  ],
  "cases": [ "*" ],
  "exclude-cases": [],
  "exclude-agent-cases": {}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants