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...
Highlighted Features jQuery Selectors Graphene gets its own @FindBy annotation and ByJQuery selector in order to fully support jQuery selectors. (read more) Injecting Selenium Resources The interesting Selenium APIs (HTML5, Mobile, etc.) can be injected to the test or page fragments directly...
Graphene 2 is building on top of the Selenium WebDriver API and provide extensions for writing reusable, robust and AJAX-enabled tests with improved readability. Graphene 2 uses the ideas from Graphene 1 (based on Selenium 1 API) and applies it to the world of Selenium WebDriver...
The Arquillian Graphene, the project focusing on making a real-browser automation a breeze, is now reaching first Final release. The Graphene is joining rest of the Arquillian party, building on top of Arquillian framework integration and Drone extension, which reached their stable version yesterday...
Goodbye, Ajocado Wait, the Ajocado project is not leaving us! It is just undergoing rename...
