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:
Hi,
I am facing issue when I say to click on Record Type and give record name. Could you please help me out.
Below is from script (because of copy paste it is not formatted)
!| script ||click on menu |Records ||search for |Automated Testing Records ||click on record type|automated testing records |
Below is from log.
2020-09-10 17:11:50,153 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoLogin - LOGIN [*****]2020-09-10 17:12:33,053 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoLogin - WAIT FOR LOGIN2020-09-10 17:12:38,276 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoMenu - WAIT FOR [Records]2020-09-10 17:12:38,286 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoMenu - CLICK [Records]2020-09-10 17:12:48,092 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoSearch - WAIT FOR SEARCH [Automated Testing Records]2020-09-10 17:12:48,147 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.TempoSearch - SEARCH FOR [Automated Testing Records]2020-09-10 17:12:57,166 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.record.TempoRecordType - WAIT FOR RECORD TYPE [automated testing records]2020-09-10 17:13:07,432 [main] ERROR com.appiancorp.ps.automatedtest.exception.ExceptionBuilder - Record Type - automated testing recordsorg.openqa.selenium.TimeoutException: Expected condition failed: waiting for presence of element located by: By.xpath: //div[contains(@class, 'CardLayout---card_item') and descendant::a[ contains(@class, 'CardLayout---accessibilityhidden') and starts-with(translate(text(),'ABCDEFGHIJKLMNOPQRSTUVWXYZ','abcdefghijklmnopqrstuvwxyz'), 'automated testing records')]] (tried for 10 second(s) with 500 MILLISECONDS interval) at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:80) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:232) at com.appiancorp.ps.automatedtest.tempo.record.TempoRecordType.waitFor(TempoRecordType.java:63)
Works well. Thanks
Hi, thanks for your question.
We typically tried to release FitNesse a week or two after a new Appian version is released. We are aware that some customers that some customers need to have the release sooner. Going forward, we will release FitNesse as soon as a new Appian version is rolled out.
Thanks.
A new update has been released with the fixes.
Is it possible to release new FitNesse updates by the time when new Appian version are rolled out? The issue is that we always have to wait for a new FitNesse update before we upgrade an environment with a new Appian version.
Thanks Vincent Wang. Appreciate your help. Any idea when this will be released?
Furthermore, we are very surprised that we as customer came across this issue. Can it be that it has not been tested by Appian? But if it has been tested by Appian, where could we have read about the incompatibility? As a result we have applied a fix to an environment which now is 'broken' (to a certain extend).
Hi Stephan Clemens brianj
Thanks for reaching out.
We are aware that the recent change broke some of the FitNesse scripts. We are working on making a minor release.
Echoing this concern. The hotfix appears to have broken record type link indexing (since they're cards) as well, which stops our tempo-based application scripts pretty early. Any plans for an updated version soon?
Dear April Schuppel,
Could it be that the latest hotfix (20.2 Hotfix Package C) broke SiteFixture.clickOnCard('foo')?
We applied the hotfix to our UAT environment and it turns out that in UAT the clickOnCard method stopped working for linked cards. Could be related to AN-163121 (Linked cards are now properly included in the list of links dialog when using assistive technologies.)?
We tried with FF and Chrome. In the environments we've not patched, our tests run perfectly fine. Whereas the tests fail in our patched UAT environment. Compare and deploy does not show any application object discrepancies between the environments.
Let me know if you have questions.
Thanks,Stephan