search

LiTiang / js-test-driver

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

Cannot specify non-root location for jsTestDriver.conf file in Eclipse plugin #157

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Go to run configurations
2. Put non-root dir for jsTestDriver.conf (e.g., engine/js/jsTestDriver.conf)
3. Click Apply
4. Navigate away from that screen, then return

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

The path I specified has been removed.  Running tests does nothing.

What version of the product are you using?

Eclipse 3.6.1
JsTestDriver 1.1.1.e

Original issue reported on code.google.com by evan.b.w...@gmail.com on 1 Nov 2010 at 6:20

GoogleCodeExporter commented 9 years ago 
I temporarily used the updated jars provided here 
http://code.google.com/p/js-test-driver/issues/detail?id=175#c1. They allow you 
to "browse" to the conf file you want. When I did, it generated a path like 
"UnitTests\conf\jsTestDriver-EventManager.conf". However, I didn't want to have 
to tell my team to use patched jars.

I would like it a lot if this issue was fixed.

Original comment by cfchris on 9 Feb 2012 at 12:30

GoogleCodeExporter commented 9 years ago 
So, stupid question...

Do you see a jstd 1.3.3.a feature when hitting the update site? You should get 
exactly what you want if you do...

Original comment by corbinrs...@gmail.com on 9 Feb 2012 at 6:00

GoogleCodeExporter commented 9 years ago 
I don't see a new version of the plugin. Attached is what I see. It has the 
update URL and all the settings in the dialog.

Original comment by cfchris on 9 Feb 2012 at 4:47

Attachments:

GoogleCodeExporter commented 9 years ago 
The update URL is this:

  http://js-test-driver.googlecode.com/svn/update

if you look around you'll see there are only old versions, and the main XML 
file in that directory is this:

  http://js-test-driver.googlecode.com/svn/update/site.xml

which refers to the least old version beneath that URL. I assume there are some 
teething problems getting this deployed.

Original comment by dominic....@gmail.com on 9 Feb 2012 at 4:55

GoogleCodeExporter commented 9 years ago 
Fixing 175 fixed this too. So you could close it as fixed.

Original comment by cfchris on 16 Feb 2012 at 3:10