Created
April 9, 2012 06:02
-
-
Save ALRubinger/2341846 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Session Title | |
Continuous Enterprise Development - Case Studies in Integration-Testing Java EE | |
Session Type | |
Conference Session | |
Session Abstract | |
In this highly-technical session, we’ll examine solutions to ease the testing of some of the more complex use-cases within Java EE. Each example will be backed by a runnable test (publicly-available to participants), and we’ll be covering automated continuous development of: | |
* The Web User Interface (via Selenium) | |
* Persistent Data and JPA | |
* Transactional Boundaries | |
* Cloud-based Deployments | |
* RESTful Endpoints | |
* ...more | |
This talk will showcase various techniques outlined in the book “Continuous Enterprise Development in Java” forthcoming from O’Reilly Media and will be delivered by the authors. Expect a lot of proof through open-source demos; through the Arquillian Platform we’ll exercise the features of any compliant Java EE6 runtime. | |
Presentation Summary | |
Companion talk for the upcoming book "Continuous Enterprise Development in Java" by O'Reilly Media, delivered by the authors (also proud 2-time JavaOne Rock Star Award winners). While this talk will be focused on development use-cases and is not an introduction to projects/products specifically, it will incorporate the use of Duke's Choice 2011 winning project Arquillian. | |
Primary Track | |
JAVAONE:Java EE Web Profile and Platform Technologies | |
Secondary Track | |
JAVAONE:Development Tools and Techniques | |
Objective 1 Introduce users to a Platform to simplify the authoring and execution of Java EE tests. | |
Objective 2 Expose proposed solutions for testing notoriously unwieldy niches of Java EE. | |
Objective 3 Prove that testing in a real runtime is essential to validate all is working; mocks are brittle. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment