Skip to content

Instantly share code, notes, and snippets.

@mojavelinux
Created January 13, 2012 08:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mojavelinux/1605104 to your computer and use it in GitHub Desktop.
Save mojavelinux/1605104 to your computer and use it in GitHub Desktop.
OSCON 2012 Proposal: Continuous Enterprise Development in Java

Submission Date: Jan 12, 2012

Proposed Title: Continuous Enterprise Development in Java

Summary:

Are you confident enough to push your application to production right now? Will it deploy? Integrate all the components? Keep the fail whale at bay? Confidence comes from tests. Real tests. Discover how to use Arquillian to develop tests that execute inside a container and gain confidence that keeps you developing, knowing your application will remain standing when faced with the real world.

Topics:

  • Tools and Techniques
  • Programming
  • Java and JVM Languages

Session type: 40-minute conference session

Abstract:

As builders of test-oriented frameworks, we’re well aware of the link between "testing" and "development". But the bond is too weak. We believe that testing is the very foundation of development--essential for learning and critical for asserting that code is consumable, complete, and correct. Yet, testing is still widely viewed as an optional part of development. Let’s collapse the gap that stands between them.

Over the past 2 years we've come to recognize that Arquillian, the testing platform we’ve developed with the JBoss community, is "The Missing Link in Enterprise Java". It’s a means for users to validate components as they're being constructed by invoking them in a real environment. Where the Java EE Specifications intentionally leave out concerns involving container interaction, Arquillian gives you convenient abstractions that bring your test to the runtime.

In the session, we'll cover:

  • Why integration tests are important
  • What's wrong with most integration tests today
  • Why testing inside a container makes a test real
  • How to write your first Arquillian test
  • How to test a myriad of Java EE technologies using Arquillian

Whether you’re learning a new technology, debugging broken behavior or laying down new code, Arquillian provides a platform for continuous development, allowing you to keep all knowledge within the system in the form of real tests.

Speakers:

  • Dan Allen
  • Andrew Rubinger
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment