Automated Testing for Appian applications

Question

Hi Everyone 
 I understand there have been questions asked in previously in the community/KB with regards to automated testing for appian applications. Most of the questions are over 1-2 years ago so I hope you don't mind of me refreshing this question. 
 I've been tasked to look at options to automate testing for our appian applications. Few high level details of our appian applications are: 
 1. hosted on-premise 
 2. based version is 18.2 
 3. have integrations with external softwares via WEB services and to network folder paths via Control M jobs 
 4. have lots of internally developed java plug-ins 
 5. ranged from development via quick-apps to highly complex customised applications 
 I understand having read all the resources in Appian community and playbook, Fitnesse for Appian is very much endorsed. Can you please advise or share your knowledge/understanding with regards to the following clarification I'm seeking on? 
 Fitness for Appian vs Selenium vs Fitnesse vs Cucumber ( https://community.appian.com/w/the-appian-playbook/102/automated-testing ) 
 The above is what's been suggested in appian playbook. 
 a) I assume Fitness for Appian is something that's been developed and community supported. How is this difference to Selenium vs Fitnesse on its own? (apology if this sounds like a silly Q) 
 b) have anyone has experience with automated testing for appian using BDD Cucumber? 
 c) and having exploring options for automated testing, these following questions are inevitable: 
 
 ease of implementation for each of the above options 
 level of skills required to build test scripts and execution 
 cost involves - (noted that Fitness for Appian is free for licenced product which apply to my case) 
 preferred option will be able to cover the testing automation required from SAIL interfaces, expression rules, to WEB services and plug-ins 
 
 Lastly, Is Jenkins purely for automating deployment? Can it be used for some level of automated testing? 
 Thank you and really appreciate any feedback/advice given. 
 Thanks 
 Julie

Kumar Agniwesh · Accepted Answer

a) I assume Fitness for Appian is something that's been developed and community supported. How is this difference to Selenium vs Fitnesse on its own? (apology if this sounds like a silly Q) 
 
Answer- Selenium is more matured testing framework and fitnesse for Appian might have some scenario where it might not be able to automate. In that case we have to wait for solution from communiy. Where as while using Selenium we have had no such issues till date. Down side is, if Appian changes the way internal code of interface- Div ID and all, we need to revisit our Selenium scripts

) have anyone has experience with automated testing for appian using BDD Cucumber? 
Answer -We are using it in our Project, we have dedicated testing team who supports and developes testing scripts for project

c) and having exploring options for automated testing, these following questions are inevitable: 
 
ease of implementation for each of the above options - Depends on Skill set you have in team, If Team has prior experience of Selenuim , they will find implementing automation testing using Selenuim more easy and vice versa 
level of skills required to build test scripts and execution- Basic to advance knwoldge of one of these frame work and Cucmber 
cost involves - (noted that Fitness for Appian is free for licenced product which apply to my case) - Not sure 
preferred option will be able to cover the testing automation required from SAIL interfaces, expression rules, to WEB services and plug-ins 
 
Also you can use Jenkins Job to trigger these scripts automatically as well as create reports as we do for any web based Applications

Automated Testing for Appian applications

Top Replies