What?

NOVA TAIG – Northern Virginia Test Automation Interest Group
September  2010 Monthly Meeting

Topic:  Java testing with Arquillian - presentation by Dan Allen

Arquillian is a container-oriented test framework that brings your test to the runtime, rather than requiring you to manage the runtime from the test.  Arquillian keeps you focused on the test case, while still being able to utilize the services provided by the container.  This talk will provide an appreciation for the productivity and coverage gained by having a component model for testing, and will explore:

  * What makes us most productive?
  * What is a component model, and how does it help?
  * Is there a component model for testing?

Presenter bio: Dan is a Principle Software Engineer at JBoss, by Red Hat, and a speaker at major industry conferences.  His technical expertise includes Java frameworks (Seam, CDI, Weld, JSF, EJB 3, JPA, Hibernate, Spring), testing frameworks (Arquillian, JUnit, TestNG, Selenium), and much more.  Dan is a dedicated Open Source and Linux advocate.

When?

Wed. September 8   6:30 – 9:00 PM

Where?
Tortilla Factory Restaurant in The Pine Shopping Center, Herndon, VA

(See web map links in upper right of this page)

    * Plenty of parking is available.
    * We have our own separate meeting room at the restaurant.
    * Food can be ordered from the menu at the meeting, for those who want appetizers, drinks, or dinner. 

    * Max number of attendees:  25

    * Menu

Cost?

No cost other than the food/drinks you order at the restaurant.

Meeting Format

* 6:30 – 7:00 Networking, food.
* 7:00 – 7:30 Each attendee introduces themselves and discusses their test automation interests/news/challenges/successes.
* 7:30 – 7:40 Announcements re job openings or those seeking work.
* 7:40 – 8:40 Topic or Presentation
* 8:40 – 9:00 Follow-on discussions

Meetings are participatory and discussion oriented.

* Meetings will be either a) informal discussion-oriented presentations or b) roundtable discussions
* Meetings may be technically-oriented at times (and may include showing and discussing code) Examples: unit testing, automation programming languages, tool specifics, security test automation, vendor presentations, load testing, code coverage, etc.
* Some meetings may be less technical and oriented to design/strategy/management subjects related to test automation. Examples: when is a software project ready for test automation, choosing a tool, open-source vs COTS, build vs buy, ROI, how to find a great test automation engineer, automation estimation, etc.
* It is expected that attendees will contribute actively to the discussions and be willing to discuss (in general terms or, if possible, specific terms) past or current automation experiences, challenges, and successes