<?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>Automating an Appian application</title><link>https://community.appian.com/discussions/f/best-practices/21380/automating-an-appian-application</link><description>Hello, 
 I have recently been hired to develop an automation framework for a large-scale Appian project. I have experience in creating automation frameworks using Selenium, Cucumber, TestNG, Junit, Maven, and Jenkins but I have never used Appian (going</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Automating an Appian application</title><link>https://community.appian.com/thread/83431?ContentTypeID=1</link><pubDate>Wed, 07 Jul 2021 19:09:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:57c21ddd-52e2-4d2b-b9cd-bc1bcf16ebbc</guid><dc:creator>jesric1029</dc:creator><description>&lt;p&gt;Thanks for the response. Someone else informed me that you can&amp;#39;t really use conditional statements with Fitnesse which would be a deal-breaker for this framework. I am thinking I&amp;#39;ll go with Selenium API and Cucumber for the test execution &amp;amp; organization. I like Cucumber because it&amp;#39;s very organized and not easy to break if you write the features well.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Automating an Appian application</title><link>https://community.appian.com/thread/83430?ContentTypeID=1</link><pubDate>Wed, 07 Jul 2021 19:07:22 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0a6ae2bb-9d63-4a9a-b8db-b5f429279bda</guid><dc:creator>juergeng0001</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;to get to the links you have to be a registered user at the Appian Community. (see the button in the right upper corner).&lt;br /&gt;The main question is, what is the best approach if Appian is changing the handling of their UI components to avoid that your QA framework is breaking.&lt;br /&gt;a.) Fitnesse for Appian&lt;br /&gt;b.) The selenium API (available at the Appian App Market)&lt;br /&gt;c.) Appian RPA (it is using the Flacon engine for recognizing UI artifacts, like icons, etc. independent of the underlying technic)&amp;nbsp;&lt;br /&gt;d.) Going with your own programming (pure Selenium) with all freedoms but the risk one day all of your testcases will stop to work.&lt;br /&gt;&lt;br /&gt;Just my two pence.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>