<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>FitNesse For Appian Driver Issue</title><link>https://community.appian.com/discussions/f/plug-ins/18004/fitnesse-for-appian-driver-issue</link><description>HI all. I&amp;#39;ve just installed FitNesse For Appian, and edited the example test as required. 
 I&amp;#39;m getting this error despite 
 reinstalling the app in different paths 
 downloading and installing the latest Chrome driver (v78) 
 tried explicitly setting</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/96731?ContentTypeID=1</link><pubDate>Fri, 24 Jun 2022 08:58:37 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:02bdc554-3300-48e3-afb3-1e242f1a99a1</guid><dc:creator>Dimitris Kazantzis</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I had the same error:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The driver executable does not exist: C:\FitNesseForAppian\null\lib\drivers\chromedriver.exe&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;After a few workarounds the issue was resolved. This was done by the following:&lt;/p&gt;
&lt;p&gt;1. Set the TESTING_HOME to fitnesse-for-appian-22.2. The file&amp;#39;s contents are shown below:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/19/Screenshot-2022_2D00_06_2D00_24-095126.png" /&gt;&lt;/p&gt;
&lt;p&gt;2. configs &amp;gt;&amp;nbsp;custom.properties file:&lt;/p&gt;
&lt;p&gt;### INSTALLATION PROPERTIES ###&lt;br /&gt;# Populate with location of this project&amp;#39;s Home Directory. Home Directory is the unzipped directory.&lt;br /&gt;&lt;strong&gt;automated.testing.home=C:\\fitnesse-for-appian-22.2&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;download.directory=C:\\Users\\dimitris.kazantzis\\Downloads&lt;/strong&gt;&lt;br /&gt;download.mime.types=application/xml,text/plain,text/xml,image/jpeg,image/png&lt;/p&gt;
&lt;p&gt;# When set to true, login will login to Tempo News, ignoring any path in the URL after /suite&lt;br /&gt;login.to.base.url=false&lt;/p&gt;
&lt;p&gt;### CHROME ###&lt;br /&gt;# Leave blank if installed in default location of: C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe&lt;br /&gt;# For MacOS or Linux/Unix, update with location of Chrome binary&lt;br /&gt;&lt;strong&gt;chrome.browser.home=C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe&lt;/strong&gt;&lt;br /&gt;# Leave blank if using the Windows driver included in TESTING_HOME\\lib\\drivers\\chromedriver.exe&lt;br /&gt;# For MacOs or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTING_HOME/lib/drivers/chromedriver-mac&lt;br /&gt;# Download new or additional drivers at &lt;a href="https://sites.google.com/a/chromium.org/chromedriver/downloads"&gt;sites.google.com/.../downloads&lt;/a&gt;&lt;br /&gt;&lt;strong&gt;chrome.driver.home=C:\\fitnesse-for-appian-22.2\\lib\\drivers\\chromedriver.exe&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The initial error occurred when I included&amp;nbsp;the contents of both files (&lt;span&gt;fitnesse-for-appian-22.2 and Automated Testing-22.2) under the same TESTING_HOME. Therefore, I would suggest separating the two folders and using only&amp;nbsp;fitnesse-for-appian-22.2&amp;nbsp;as the TESTING_HOME.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/75802?ContentTypeID=1</link><pubDate>Wed, 05 Aug 2020 08:08:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ae989eb8-74e2-4a88-aff9-ab675173ac2e</guid><dc:creator>qazia</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Was this issue resolved ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;and how did you fix it ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/73188?ContentTypeID=1</link><pubDate>Wed, 08 Apr 2020 22:31:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:dc042625-d3c9-4712-9e56-53ec3bb7039c</guid><dc:creator>sajals</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am still getting the error even my testing home is- C:\\FitNesseForAppian&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;Error :&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The driver executable does not exist: C:\FitNesseForAppian\null\lib\drivers\chromedriver.exe&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Below is my custom properties file:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;automated.testing.home=C:\\FitNesseForAppian&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;FITNESSE_FOR_APPIAN_VERSION=v20.1&lt;br /&gt;download.directory=C:\\FitNesseForAppian\\Downloads&lt;br /&gt;download.mime.types=application/xml,text/plain,text/xml,image/jpeg,image/png&lt;/p&gt;
&lt;p&gt;# When set to true, FitNesse tests will login to Tempo News, ignoring any path in the URL after /suite&lt;br /&gt;login.to.base.url=false&lt;/p&gt;
&lt;p&gt;### CHROME ###&lt;br /&gt;# Leave blank if installed in default location of: C:/Program Files (x86)/Google/Chrome/Application/chrome.exe&lt;br /&gt;# For MacOS or Linux/Unix, update with location of Chrome binary&lt;br /&gt;chrome.browser.home=&lt;br /&gt;# Leave blank if using the Windows driver included in TESTING_HOME/lib/drivers/chromedriver.exe&lt;br /&gt;# For MacOs or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTING_HOME/lib/drivers/chromedriver-mac&lt;br /&gt;# Download new or additional drivers at &lt;a href="https://sites.google.com/a/chromium.org/chromedriver/downloads"&gt;sites.google.com/.../downloads&lt;/a&gt;&lt;br /&gt;chrome.driver.home=&lt;/p&gt;
&lt;p&gt;### FIREFOX ###&lt;br /&gt;# Leave blank if installed in default location of: C:/Program Files (x86)/Mozilla Firefox/firefox.exe&lt;br /&gt;# For MacOS or Linux/Unix, update with location of Firefox binary&lt;br /&gt;firefox.browser.home=&lt;br /&gt;# Leave blank if using the Windows driver included in TESTING_HOME/lib/drivers/geckodriver.exe&lt;br /&gt;# For MacOS or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTINGHOME/lib/drivers/geckodriver-mac&lt;br /&gt;# Download new or additional drivers at &lt;a href="https://github.com/mozilla/geckodriver/releases"&gt;github.com/.../releases&lt;/a&gt;&lt;br /&gt;firefox.driver.home=&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/70850?ContentTypeID=1</link><pubDate>Fri, 06 Dec 2019 09:34:01 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d07b7d6f-91ec-4c94-8f32-541dfc86ab55</guid><dc:creator>alland</dc:creator><description>&lt;p&gt;Hi Vincent.&lt;/p&gt;
&lt;p&gt;A little more experimentation has solved the issue, thanks for the pointers.&lt;/p&gt;
&lt;p&gt;The documentation at &lt;a href="/w/the-appian-playbook/97/automated-testing-with-fitnesse-for-appian"&gt;https://community.appian.com/w/the-appian-playbook/97/automated-testing-with-fitnesse-for-appian&lt;/a&gt;&amp;nbsp;contains the line &amp;#39;&lt;span&gt;automated.testing.home to be TESTING_HOME (e.g. C:\FitNesseForAppian)&lt;/span&gt;&amp;#39;, which to me suggests that the home can be anything as long as &lt;span&gt;TESTING_HOME is defined in the config.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It would appear that something is hardcoded that breaks this standard though, as I finally got it to work ONLY when I had&amp;nbsp;C:\FitNesseForAppian as the root folder, or as you say above, if the root contains&amp;nbsp;\FitNesseForAppian.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;A subtle point I know but its taken a while to resolve owing to the confusion.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks again for your help though!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/70836?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 17:12:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4233e083-dcd4-4757-a4b3-8166dca28807</guid><dc:creator>Vincent Wang</dc:creator><description>&lt;p&gt;It looks like you have created a folder called FitNesse inside your C drive&lt;br /&gt;So you will need to set the automated.testing.home to C:\\FitNesse\\FitNesseForAppian&lt;/p&gt;
&lt;p&gt;Could you also manually verify that there is a FitNesseForAppian folder inside your C:\\FitNesse folder?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/70835?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 17:06:33 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:1620c485-7968-45ba-8df1-8a409b1883a9</guid><dc:creator>alland</dc:creator><description>&lt;p&gt;Hi Vincent,&lt;/p&gt;
&lt;p&gt;Thanks for responding...&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve got the&amp;nbsp;&lt;strong&gt;chrome.driver.home&amp;nbsp;&lt;/strong&gt;blank as per the instructions (I&amp;#39;m using the default driver location), but when I tried&amp;nbsp;coding the path directly I did use escaped backslashes.&lt;/p&gt;
&lt;p&gt;My custom properties file is below. Note that I&amp;#39;ve altered the &lt;span&gt;automated.testing.home since I posted the screenshot, but I still get the same /null/ segment inserted into the drivers URL.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;(&amp;#39;ve also tried adding&amp;nbsp;C:\\FitNesse\\ to see if that helped, but no)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;------------------------------&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;automated.testing.home=C:\\FitNesse&lt;/p&gt;
&lt;p&gt;FITNESSE_FOR_APPIAN_VERSION=v19.2&lt;br /&gt;download.directory=C:\\FitNesse\\Downloads&lt;br /&gt;download.mime.types=application/xml,text/plain,text/xml,image/jpeg,image/png&lt;/p&gt;
&lt;p&gt;# When set to true, FitNesse tests will login to Tempo News, ignoring any path in the URL after /suite&lt;br /&gt;login.to.base.url=false&lt;/p&gt;
&lt;p&gt;### CHROME ###&lt;br /&gt;# Leave blank if installed in default location of: C:/Program Files (x86)/Google/Chrome/Application/chrome.exe&lt;br /&gt;# For MacOS or Linux/Unix, update with location of Chrome binary&lt;br /&gt;chrome.browser.home=&lt;br /&gt;# Leave blank if using the Windows driver included in TESTING_HOME/lib/drivers/chromedriver.exe&lt;br /&gt;# For MacOs or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTING_HOME/lib/drivers/chromedriver-mac&lt;br /&gt;# Download new or additional drivers at &lt;a href="https://sites.google.com/a/chromium.org/chromedriver/downloads"&gt;sites.google.com/.../downloads&lt;/a&gt;&lt;br /&gt;chrome.driver.home=&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FitNesse For Appian Driver Issue</title><link>https://community.appian.com/thread/70828?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 16:06:19 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b57fdd37-f2fd-471e-9550-2f2ea80b8a4f</guid><dc:creator>Vincent Wang</dc:creator><description>&lt;p&gt;This could be due to windows&amp;nbsp;format for &amp;quot;\&amp;quot;, can you share what you put for&amp;nbsp;&lt;span&gt;&lt;strong&gt;chrome.driver.home&lt;/strong&gt; in the custom properties file?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>