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:
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
Discussion posts and replies are publicly visible
JulieMc Hi Julie. I work at Appian's Customer DevOps team and we are actually aiming to integrate Cucumber testing within Appian for our 19.1 release. I'm personally driving this effort myself and we are looking to make it very easy and simple to write Cucumber tests for your Appian applications. Let me know if you have any questions about this and I would be happy to answer them.
Ah I may have misspoke about the Appian release. We actually release our products on the same lifecycle as Appian but not necessarily just for that Appian release. So when we introduce Cucumber for Appian alongside the Appian 19.1 release next quarter, it will be backwards compatible for all supported Appian versions. So you can use the Cucumber for Appian tool on your v18.1 sites no problem. The release for the tool is simply scheduled for next quarter. If you want a preview for what methods Cucumber for Appian will support, I recommend trying out our FitNesse For Appian tool (community.appian.com/.../automated-testing-with-fitnesse-for-appian) as Cucumber For Appian will basically mirror all that functionality. The CheatSheet provided in the FitNesse For Appian tool will show all the methods we currently support. You can count on all those methods being supported in Cucumber For Appian as well