LiTiang / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

Problem with relative paths in config since version 1.3.2 #223

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

My project layout (simplified):
/lib.js
/js/jsTestDriver.conf
/js/test/libTest.js

The jsTestDriverConf:
server: http://localhost:9876
load:
  - ../lib.js
test:
  - test/*.js

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

When I execute (with /js being the current folder), the compiler says:
    error loading file: /test/../lib.js: [object Event]
    error loading file: /test/test/libTest.js: [object Event]

Even though it finds the file, because when I give a wrong path to lib.js, it 
says the usual:
java.lang.IllegalArgumentException: The patterns/paths used in the 
configuration file didn't match any file, the files patterns/paths need to be 
relative

What version of the product are you using? On what operating system?
JsTestDriver-1.3.2.jar
Mac OS X 10.6.7

Please provide any additional information below.
I've attached a sample of my setup that will produce the error (execute with 
/js as the current folder)

Original issue reported on code.google.com by meyer...@gmail.com on 4 Apr 2011 at 4:49

Attachments:

GoogleCodeExporter commented 9 years ago
Should we re-open this?  Start a new one?  I've tested this on Windows 7 too, 
still a problem.  I need to pass parameters in the browser element, so I need 
1.3.4 or later.  I'm working around it by running jstd through vanilla exec 
plugin.  It feels like such a hack..

Original comment by paul.hic...@gmail.com on 1 Aug 2013 at 9:40

GoogleCodeExporter commented 9 years ago
The world has moved on. Nowadays the cool people are using Karma test runner 
instead of jstd. Way faster and more stable. 

Original comment by romulu...@gmail.com on 2 Aug 2013 at 5:03