Software Testing Analysis & Review 2006 Conference Proceedings 

Home


GENERAL INFO.

Register

Get a Brochure


PRESENTATIONS

Keynotes

Tutorials

Concurrent

Master Schedule


IN THE EXPO

Sponsors

Exhibitors

To Exhibit


MORE INFO.

SQE Home

Other Conferences


Email Software Quality EngineeringRegister Now

Software Quality Engineering



                
STAREAST 2006 Concurrent Sessions

Go To:  Agile Methods  |  Exploratory Testing  |  Outsourced Testing  |  Performance Testing  |  Security Testing  |  
Special Topics  |  Test Automation  |  Test Management  |  Test Metrics  |  Test Techniques


View by Date

 Test Automation
T3
Thursday, May 18, 2006 9:45 AM
Tester Skills for Moving Your Automation to the Next Level
Dion Johnson, DiJohn Innovative Consulting, Inc.

Job interviews for test automation engineers are often limited to, "How proficient are you with the tool vendor XYZ’s scripting language?" This approach does little to help the hiring manager choose those individuals who are or will become highly skilled automation professionals. As a test engineer, you will need to acquire specialized knowledge and tool independent capabilities to become a test automation expert. Join Dion Johnson as he identifies the core set of tool-independent competencies required of a successful automated software test engineer: automation framework design, programming and debugging skills, object model concepts, and automation methods based on the required quality attributes. Learn how you, as a hiring manager, can identify these skills, or find out how you personally can improve your skills to become a true test automation expert.

• Skills to screen test automation candidates or market yourself as an automated test engineer
• Crucial automated testing concepts and knowledge domains
• Required automated test frameworks and skills
T7
Thursday, May 18, 2006 11:15 AM
“How to Build a Better Test Script” with a Component-Based Approach
Jeff Roberts, Convergys

Do you dream of having a centralized, modular set of test script steps or “components” that you can link together many times in multiple test scripts to create end-to-end fully automated tests? If so, join Jeff Roberts as he lays out, step-by-step, the real-life method his company has used for the past four years to do just that. With a database of script components, they write functional test scripts more quickly and, as the software changes, update them more efficiently. In a presentation detailing how this process was used in a real-world setting, Jeff explains the approach adopted by his large testing organization with multiple products and teams operating in multiple locations. Learn to break down your scripts into standardized components categorized as procedures, how-to information, data, and SQL commands. Take back the basics of a complete methodology for building and maintaining better test scripts.

• The methodology for component-based test scripts
• An example of the components and a test script composed using this approach
• Implementing the component-based test scripting in your company
T12
Thursday, May 18, 2006 1:30 PM
Automated Setup and Tear Down of Complex, Multi-tier Test Configurations
James Phillips, Akimbi Systems

Many software test and development teams struggle to test systems with complex set-up steps and multiple configurations. With these interdependent software systems, testers must iterate through very large, multi-dimensional test matrixes (for example, permuting front-, middle-, and back-tier platforms) to complete the test requirements. Testers have the difficult and sometimes seemingly impossible task of duplicating failures and saving the system’s state for later analysis and debugging. With several emerging commercial software tools, software development organizations can successfully implement live-state software test configuration provisioning and capture systems. James Phillips shares case studies of organizations that maintain comprehensive libraries of system environments used for repeated testing and organizations that give every developer and test engineer the equivalent of a fully equipped data center with dedicated provisioning staff.

• Pool and share server, networking, storage, and other resources between development and test teams
• Automatically set up and tear down complex, multi-machine software configurations
• Suspend and capture “live” multi-machine environments for both development and test
T17
Thursday, May 18, 2006 3:00 PM
Don't Whine—Build Your Own Test Tools
Clay Bailey, IBM

The highly customized hardware-software system making up the new flight operations system for the world’s largest airline did not lend itself to off-the-shelf tools for test automation. With a convergence of on-demand, highly available technologies and the requirement to make the new system compatible with hundreds of legacy applications, the test team was forced to build their own test software. Written in Java, these tools have helped increase test coverage and improved the efficiency of the test team. One tool compares the thirty-one year old legacy system with its new equivalent for undocumented differences. Clay Bailey will demonstrate these tools, including one that implements predictive randomization methods and another that decodes and manipulates hexadecimal bit string representations.

• Custom test tools for a unique systems environment
• Innovative ways to develop and use Java for writing test tools
• A novel way to manage ongoing change in regression test suites



STAR<i>EAST</i> 2006 is a Software Quality Engineering Production

The Current Conference   |   StickyMinds.com   |   Better Software magazine

Software Quality Engineering   •   330 Corporate Way, Suite 300   •   Orange Park, FL 32073

Phone: 904-278-0524   •   Toll Free: 800-423-8378   •   Fax: 904-278-4380   •   Email: sqeinfo@sqe.com

© 2006 Software Quality Engineering. All rights reserved.