I am trying to implement automation using ‘Cucumber for Appian’ in our project (our project is based on Appian). I am facing challenges/questions while implementing this which are described as below:
Unfortunately this method is proving unsuccessful .Can you please provide your inputs as to a solution here?
2. As we are trying to achieve maximum automation coverage, we want to utilize custom code that extends beyond functions in the cheat sheet for example:
Is there a manner by which we could do this and would it be feasible to edit the Appian provided jar file to cater for this? If yes, can you please help us with steps as to how to implement this?
3. The script is running fine on Chrome browser but gives object identification issues on IE (The objects which are working correctly on Chrome are not getting identified on IE). Can you please suggest what may be the cause?
4. How can we get updates on the latest JAR files or for any other component upgrades so that we can incorporate these into our framework.
Please let me know the solutions for above issues so as we can proceed ahead with our scripting on ‘Cucumber for Appian’.
You can extend the Appian Cucumber Jar with your own Glue Code and step definitions, you'll have to know how to write java and work with maven, I've had success with custom methods.
Can you provide the errors / stack traces that are occurring?
Upgrading the Jars is simple, replace the jar file and update the `pom.xml` file with the new version number
Not the OP, but just wanted to check, How did you achieve this?
Anyway we can get the driver instance and use it in custom code?
I am looking for the classes from the existing appian jar that needs to be imported in the new step definition class to pass the values from and between the existing jar and the newly created step definition class. Kindly help
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.