Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
7 subscribers
Views
2953 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Hi I am using the AutomatedTesting-1.2.5 shared component. While i am trying to
Priya
over 9 years ago
Hi I am using the AutomatedTesting-1.2.5 shared component. While i am trying to execute the logintest script I am getting the below error
__EXCEPTION__:java.lang.IllegalStateException: The driver executable does not exist: D:\\Softwares\\Appian\\AutomatedTesting\
ull\\lib\\drivers\\chromedriver.exe
I could note that its looking for lib inside null directory in the path i have specified. If i create the folder null inside the installation directory its working as expected. I updated the TESTING_HOME to a dummy directory to test if still null folder is appended. I noticed that the path is not taken from the path defined in the script. I assume that its taken from the fitnesse.properties file. Kindly let me know if I am missing any configuration.
OriginalPostID-208775
OriginalPostID-208775
Discussion posts and replies are publicly visible
0
Michael Chirlin
Appian Employee
over 9 years ago
Do you have a custom.properties file in AUTOMATED_TESTING_HOME/configs?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Priya
over 9 years ago
No I don't have that property file.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
praveenb
over 9 years ago
I have faced same problem , but am tried to below path in fitnesse configurations
!*** FitNesse Configurations
!define TEST_SYSTEM {slim}
!path D:\\AutomatedTesting-1.2.5
!path D:\\AutomatedTesting-1.2.5\\**.jar
***!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Michael Chirlin
Appian Employee
over 9 years ago
I've now realized that the release on shared components is missing some crucial pieces.
For everything to work correctly do the following:
* Create a folder in TESTING_HOME called configs
* Copy the attached custom.properties into it
* Update automated.testing.home in that file to point at your TESTING_HOME
* Replace your start.bat file with the version attached.
custom.properties
start.bat
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Michael Chirlin
Appian Employee
over 9 years ago
Then in fitnesse you no longer need to point to your testing home, you can instead use:
!path ${automated.testing.home}\\**.jar
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Michael Chirlin
Appian Employee
over 9 years ago
I will be updating the shared component shortly.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Priya
over 9 years ago
Thanks Michael.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel