--port needs to be specified even if it's in the config

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create a config file with server: http://localhost:8181 and js files to test 
(e.g., altConfig.conf)
2. attempt to run the server with "java -jar JsTestDriver.jar --config 
altConfig.conf"

What is the expected output? What do you see instead?

Server should read conf and start server on port 8181. Instead server does not 
start, and output the --help documentation. 

However if you run the exact same command with --port 8181 specified the server 
will start and read the config file.

What version of the product are you using? On what operating system?
jsTestDriver-1.3.2.jar, Ubuntu 8 LTS

Original issue reported on code.google.com by jared.mc...@gmail.com on 27 Jun 2011 at 8:41

[GoogleCodeExporter]

http://code.google.com/p/js-test-driver/wiki/ConfigurationFile#server:

Please reread the server definition, as it relates to defining the server to 
run tests against.

I'll leave this as an enhancement.

Original comment by corbinrs...@gmail.com on 28 Jun 2011 at 3:52

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I guess I'm not getting something the documentation seems to support the 
behaviour I'm trying to achieve. 

I tried defining a default location for my server/port in my config but the 
jsTestDriver won't read the config unless I override the port in the CLI.

Original comment by jared.mc...@gmail.com on 28 Jun 2011 at 1:12

[GoogleCodeExporter]

http://code.google.com/p/js-test-driver/wiki/CommandLineFlags#--server might 
clarify.

Essentially, the server flag and configuration attribute declare what server to 
run tests on. It does not declare what server to start tests on.

For that, you need the --port flag which tells jstd what port to start the 
server on. Currently, there is no way to declare the port in the configuration 
file.

Original comment by corbinrs...@gmail.com on 28 Jun 2011 at 2:32