Arquillian with JScript / Selenium -- Best Practices and Limitations

[Chuck Staples]

My organization is increasing testing focus on an Angular-based UI. So far our test automation has had limited JScript interaction, and we are investigating tools which can improve on Selenium integration limitations with JavaScript. Could the use of Arquillian and its extensions help here? If so, what significant improvements to Selenium-JScript integration could it provide? What would be a sample set of best practices and limitations?

[Jason Porter]

Are you looking to test just the client side JavaScript or any back end services as well?

[Chuck Staples]

Client-side; GUI manifestation of the backend data and its transformations -- presentation, format, consistency, some limit/sanity checks. (We have separate non-Java tests for the backend data.) In general, the UI tests will call for a report (or set of reports) and check its existence, data population, unit of measurement display, rendering performance, etc. We've typically used specific Selenium WebDriver calls to access the affected objects directly by XPath.

(There are efforts to quantify backend performance as well, but that's another set of teams, and not specifically in my focus. Always willing to share, though... )

[Jason Porter]

Arquillian uses Selenium in Arquillian Drone and Arquillian Graphene, but if you already have something up and running there may not be much that it will help you with. Arquillian Drone does all the driver setup and adds some nice features around PageObjects, but again, if you're already using those techniques it won't bring a lot to the table, but it may help simplify a few things.

There are also some nicities for Angular in Graphene, but that's about all it will get you for client side.

[Chuck Staples]

Well, if anything it's an excuse to look at it. Appreciate the info.