Java EE, Testing, Fast Turnaround
Once you started developing some integration tests, you should also think about how and where to run them. The last part of this series is dedicated to running tests in continuous integration...
We have previously discussed which technologies to use and how to improve the test development turnaround when we want to test JSF with Arquillian. However developing tests using the right tools used the right way isn’t the last stop in a development cycle...
In a previous post we have discussed what technologies we use for testing JSF and RichFaces in particular. The tools we use focus on testing complex business applications with rich user interfaces...
As we announced earlier, we are undergoing several changes in our approach to how RichFaces is tested. We already have an extensive functional test suite authored by a top-notch RichFaces QE team, but this suite doesn’t allow us to react quickly on regressions introduced and so we usually find some of them during release testing...
It has been a pretty long road from Alpha1 to this release, focused primarily on polishing the user experience. So without any further ado, let’s look at the new shiny features!..
Have you ever wanted to test a web application using real HTTP requests, but still have the opportunity to verify server-side state and behavior? Wouldn’t it be great to have the full power of Arquillian Drone, driving Selenium or WebDriver on the client, then combine that with an Arquillian in-container test? Now you can! Ike’s innovative army has created yet another powerful weapon for your testing arsenal, Arquillian Warp...
