Home arrow 2007 Half-Day Workshops
International Software Testing Conference
Home
About The Conference
Organizers
2007 Security Speakers
2007 Security Testing Talks
2007 Quality Testing
2007 Keynote Speeches
2007 Sponsors
2007 Half-Day Workshops
VERIFY 2007 Conference
Mailing List

Enter your email to receive occasional news about VERIFY 2008.

2007 Half-Day Workshops
W11:Best practices in gathering, analyzing & writing testable requirements-Rebecca Staton-Reinstein PDF Print E-mail
Study after study shows the same unhappy news…over half of all defects arise during the requirements phase of a project but we don’t find them until the testing phase of the project or even in production.  There are 8 best practices that can be added to any requirements methodology that will bring down the rate of defects dramatically including involving testers in the requirements process.  Learn these 8 best practices and start improving your requirements and project results immediately.
Digg!Reddit!Del.icio.us!Google!Netscape!Technorati!StumbleUpon!Newsvine!Yahoo!

Last Updated ( Saturday, 27 October 2007 )
W12: Getting a Handle on Risk: Risk Based Testing Strategies - Clyneice Chaney PDF Print E-mail
With the rapid pace of application development in the e-business world, testing has become a challenging proposition. Trying to meet even tighter deadlines while still delivering products that meet customer requirements is the greatest challenge testers face today. Formulating answers to age-old questions like “What should we test?” and “How long do we test?” requires different strategies in fast-paced environments.

Stakeholders are looking for testers to provide answers to additional questions such as:

• Does the product meet our quality expectations?
• Is the application ready for users?
• What can we expect when 2,000 people hit the site?
• What are we risking if we release now?

Meeting the Demands One way for testers to meet the demands of rapid application implementation is to use a risk-based approach to defining requirements and strategy. Such an approach allows you to assess the risks of potential problems in the product compared to the quality expectations that a stakeholder has. A sound risk-based test strategy can increase the probability that:

• The most important problems are found
• Problems are detected early
• Problems with the most potential rework are found first
• Requirements with the most impact to users are tested first
• Accurate information on product quality can be provided

The proposed risk strategy for testing moves us from the informal approach experienced testers often use to a more formal and systematic way of assessing risk that allows you to base your test strategy on the assessment as well as address the quality concerns of the stakeholder.

With the rapid pace of application development, testing has become a challenging proposition. Trying to meet tight deadlines and deliver products that meet customer requirements is the greatest challenge testers face today. This presentation discusses a risk assessment approach that is used to assess risks associated with product testing. The assessment approach provides an alternative to “guesses” about what should be tested, and helps test managers determine where they should concentrate their efforts.

Digg!Reddit!Del.icio.us!Google!Netscape!Technorati!StumbleUpon!Newsvine!Yahoo!

Last Updated ( Saturday, 27 October 2007 )
W21: Jumpstart Your Functional Test Automation with Canoo WebTest - Nate Oster PDF Print E-mail
In this series of exercises, an experienced Canoo WebTest user explains how to quickly become productive with this popular open source framework for functional software test automation. Using working code and common problems facing agile testers, this session provides new users what they need to achieve high levels of maintainable test automation. From that foundation, we'll also cover more advanced topics like test-first design, naming conventions, continuous build integration, and test automation patterns from real agile projects.

This isn't a sanitized demo - you'll leave this workshop knowing how to create and maintain WebTests for your own web applications.

Notes: This tutorial is a series of instructor-led, incrementally more complex pair-programming exercises

This tutorial is based on training material originally developed for new testers on a 9-person agile test team. The examples are expanded to be more broadly applicable and use a publicly available application.

Digg!Reddit!Del.icio.us!Google!Netscape!Technorati!StumbleUpon!Newsvine!Yahoo!

Last Updated ( Saturday, 27 October 2007 )
W22: Creating & Leading the High Performance Test Organization - Bob Galen PDF Print E-mail
Let’s face it. The challenges in software teams are ever increasing – less people, less time, technologies changing constantly, and ever increasing business expectations, are clearly the norms in today’s teams. Nowhere is this more self-evident than within testing teams, since the pressure increases as we move down through the life-cycle.

This creates a tremendous leadership challenge for testing team managers, group leaders or anyone chartered with directing testing. However, there is a “good news” aspect to this challenge. The opportunity is ripe for effective test leaders to differentiate themselves and their teams as they meet and exceed organizational expectations. You just need to tools and the will.

This workshop focuses on acquiring the fundamental skills to become that outstanding test leader. It will explore –

• How to build, motivate and lead great testing teams
• How to create impact driven communications on testing state
• How to properly plan and execute your teams evolution, growth and ability to meet project challenges
• How to handle some of the toughest “people” challenges facing good managers
• How to be agile and adaptable – learning to change with the organizational landscape

Digg!Reddit!Del.icio.us!Google!Netscape!Technorati!StumbleUpon!Newsvine!Yahoo!

Last Updated ( Saturday, 27 October 2007 )