HI all. I've just installed FitNesse For Appian, and edited the example test as required.
I'm getting this error despite
reinstalling the app in different paths
downloading and installing the latest Chrome driver (v78)
tried explicitly setting the chrome.driver.home in custom.properties file
despite these efforts, the NULL fragment persists.
The driver executable does not exist: C:\FitNesse\FitNesseForAppian\null\lib\drivers\chromedriver.exe
Does anyone know what the issue might be?
This could be due to windows format for "\", can you share what you put for chrome.driver.home in the custom properties file?
Thanks for responding...
I've got the chrome.driver.home blank as per the instructions (I'm using the default driver location), but when I tried coding the path directly I did use escaped backslashes.
My custom properties file is below. Note that I've altered the automated.testing.home since I posted the screenshot, but I still get the same /null/ segment inserted into the drivers URL.
('ve also tried adding C:\\FitNesse\\ to see if that helped, but no)
# When set to true, FitNesse tests will login to Tempo News, ignoring any path in the URL after /suitelogin.to.base.url=false
### CHROME #### Leave blank if installed in default location of: C:/Program Files (x86)/Google/Chrome/Application/chrome.exe# For MacOS or Linux/Unix, update with location of Chrome binarychrome.browser.home=# Leave blank if using the Windows driver included in TESTING_HOME/lib/drivers/chromedriver.exe# For MacOs or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTING_HOME/lib/drivers/chromedriver-mac# Download new or additional drivers at sites.google.com/.../downloadschrome.driver.home=
It looks like you have created a folder called FitNesse inside your C driveSo you will need to set the automated.testing.home to C:\\FitNesse\\FitNesseForAppian
Could you also manually verify that there is a FitNesseForAppian folder inside your C:\\FitNesse folder?
A little more experimentation has solved the issue, thanks for the pointers.
The documentation at https://community.appian.com/w/the-appian-playbook/97/automated-testing-with-fitnesse-for-appian contains the line 'automated.testing.home to be TESTING_HOME (e.g. C:\FitNesseForAppian)', which to me suggests that the home can be anything as long as TESTING_HOME is defined in the config.
It would appear that something is hardcoded that breaks this standard though, as I finally got it to work ONLY when I had C:\FitNesseForAppian as the root folder, or as you say above, if the root contains \FitNesseForAppian.
A subtle point I know but its taken a while to resolve owing to the confusion.
Thanks again for your help though!
Discussion posts and replies are publicly visible
© 2019 Appian. All rights reserved.