One of my friends and former co-worker Rick Hower is starting
a Northen Virginia Test Automation Interest Group. I will be there.
If you are in the DC metro area and this is of interest to you I encourage
you to be there. The meeting details are below.
NOVA TAIG - Northern Virginia Test Automation Interest Group Monthly meetings beginning in January 2009.
Meetings will be on Wednesday nights 6:30 – 9:00; no cost other than food you order and your active participation in meeting discussions.
First meeting Wednesday January 7 2009 (Next meeting is being planned for early February)
INITIAL TOPIC JAN 7:
Test Automation Frameworks: Roundtable discussion (see more info below).
Send e-mail to Rick Hower firstname.lastname@example.org to reserve a spot if you are planning to attend.
Meetings will be held in the Reston-Herndon area, usually at a local restaurant or company facility. Specific meeting location will be sent in response to reservations.
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 automation job openings or those seeking test automation work.
7:40 - 8:40 Topic or Presentation
8:40 - 9:00 Follow-on discussions
INITIAL TOPIC JAN 7: Test Automation Frameworks: Round table discussion re: what is meant by a ‘framework’?, what types of reusable functionality/components/services/practices should be in a framework?, how can frameworks help with management/planning/ROI? Note: We will also spend some time at the January meeting discussing suggestions for upcoming meeting topics.
IF YOU ARE PLANNING TO ATTEND:
Please email email@example.com if you are planning to attend the meeting so we can a) let you know the specific meeting location b) so that you can be notified of any last minute meeting location changes.
The meetings will be participatory and discussion oriented.
--There will not be a presentation at the first meeting, but it is expected that future meetings will often include informal discussion-oriented presentations.
--Meetings are expected to 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 are expected to be less technical and oriented to design/strategy/management subjects related to test automation. Examples: determining when a software project is 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