Overview
FitNesse for Appian is a client-side tool that makes it easy to create automated tests on the Appian platform. Create test scripts that will run Appian as if a user was clicking through the application and filling out data. FitNesse for Appian includes easy instructions to get you started.
Note: Java 11 required for plugin version 23.4
Key Features & Functionality
With FitNesse for Appian, you can:
Reusable scripts can be written to:
you can use |click on button|Create Price Quote|you should look into the code that developer set label for that button what is it.
I am trying to click on a button in a page
I am trying to click on a button in a page but it is not working with name and index.. Can u help me on that?
and if i use the lib folder as is i am getting below error . any suggestions.
PS C:\WorkFolder\test\AUtomated_Tests\selenium_tests> cucumber '\features\feature_files\automation_regression_EASi-16694\EASi-16695\PR_Team_With_Edit_Right_can_Edit_PR.feature'cannot load such file -- ./FitNesseForAppian/lib/accessors-smart-2.4.9.jar (LoadError)<internal:C:/Ruby/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'<internal:C:/Ruby/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'C:/WorkFolder/test/AUtomated_Tests/selenium_tests/ruby_methods/tempo_fixture.rb:2:in `block in <top (required)>'
Appreciate the help
i am new to this and everywhere i looked the jar file has a folder fitness application and which contains fitness for appian jar in lib folder. this jar file does not contain those am i looking at wrong place?
Hi Team, There seems to a glitch with the login in the new version.
java.lang.IllegalArgumentException: Keys to send should be a not null CharSequence
Could you please check & confirm?
execution Log below
Picked up _JAVA_OPTIONS: -Djavax.net.ssl.trustStoreType=Windows-ROOT 11:38:48.634 [main] ERROR com.appiancorp.ps.automatedtest.exception.ExceptionBuilder - Login page - appianFitnesse java.lang.IllegalArgumentException: Keys to send should be a not null CharSequence at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:98) ~[selenium-remote-driver-4.8.2.jar:?] at com.appiancorp.ps.automatedtest.tempo.TempoLogin.login(TempoLogin.java:136) [appian-selenium-api-23.1.1.jar:?] at com.appiancorp.ps.automatedtest.fixture.BaseFixture.loginIntoWithUsernameAndPassword(BaseFixture.java:438) [appian-selenium-api-23.1.1.jar:?] at com.appiancorp.ps.automatedtest.fixture.BaseFixture.loginIntoWithUsername(BaseFixture.java:467) [appian-selenium-api-23.1.1.jar:?] at com.appiancorp.ps.automatedtest.fixture.BaseFixture.loginWithUsername(BaseFixture.java:478) [appian-selenium-api-23.1.1.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_261] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_261] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_261] at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_261]
Issue resolved in this latest version release v23.1.1