The Latest
Get Control of Your Test Automation Project[presentation] Developing an automated regression test bed is no easy task. In fact, according to recent studies, more than 50 percent of test automation projects fail. |
Jeff Tatelman, Spherion Technology Architects
|
|
Measuring the Effectiveness of Automated Functional Testing[presentation] Many struggle to accurately judge the value, success, and return on investment of test automation. |
Ross Collard, Collard & Company
|
|
Deliver Reliable Applications Faster With the Right Tools and Processes[presentation] Repeated attempts to decrease software time-to-market have borne a variety of processes and methodologies, resulting in dynamic development and testing environments that continue to ignore quality issues as well as budget constraints. |
Dave Kapelanski, Compuware Corporation
|
|
Software Test Automation Spring 2002: Test Automation on a Shoestring: Doing More with Less[presentation] Want to automate your tests but don't have the budget for big-league tools? Elisabeth Hendrickson offers case studies where test automation was accomplished with simple tools for small budgets. |
![]() |
|
Lessons Learned in Test Automation[presentation] Can test automation really advance your testing mission? The answer to that question is a resounding "That depends!" But to make it happen you have to provide value to development and find new ways of testing. |
Bret Pettichord, Pettichord Consulting
|
|
The Past, Present, and Future of Software Test Automation Tools[presentation] Gregory Pope examines the past, present, and future of software testing tools. By contrasting the best thinking of ten years ago with what's happening today, he brings a clear and unique perspective to what the future might hold. |
![]() |
|
How Many Testers Is Enough?[article] This article takes a seemingly simplistic view at managing resources and projects. |
Robert Rivera
August 8, 2002 |
|
Taking Test Automation Mainstream[presentation] By now, most test organizations have implemented at least one test automation tool. However, the success of these tools is by no means guaranteed. Why is it that these products often fail to meet their potential? |
![]() |
|
Performance: The Overlooked Quality Metric[presentation] The amount of time allocated to quality testing is always under pressure due to slippage in development and delivery dates-this often results in performance testing being overlooked in the quality process. |
Ernest Huber, TCI Solutions, Inc.
|
|
Software Test Automation Spring 2002: Test Automation With Action Words: A Practical Experience[presentation] Action Word Testing. This concept illuminates testing as an action, a process, an art. |
|
|
A Practical Approach to Early-Cycle QA Test Automation[presentation] Everyone knows that a large body of automated unit tests for classes, subsystems, and frameworks adds to overall code quality. |
Michael Silverstein, SilverMark, Inc.
|
|
Effective Test Automation and Deployment Strategy for Java Servlet and JSP Applications[presentation] Recent advances in Java servlet and JSP technology have gained popularity and support from the industry. The backbone of this technology is the J2EE platform and Model 2 JSP architecture which effectively separate presentation from content. |
Heesun Park, SAS Institute
|
|
Testing in the Fast Lane: Automated Acceptance Testing in an eXtreme Programming Environment[presentation] Are you looking to apply the values of eXtreme Programming (XP) to test automation? In eXtreme Programming Explained, Kent Beck compares XP to driving a car-meaning the team must make constant corrections to stay on track. |
![]() |
|
Software Test Automation Fall 2001: Test Automation with Action Words: A Practical Experience[presentation] Action Word Testing. This concept illuminates testing as an action, a process, an art. |
|
|
Adventures in Session-Based Testing[article] This paper describes the way that a UK company controlled and improved ad-hoc testing, and was able to use the knowledge gained as a basis for ongoing, sustained product improvement. It details the session-based methods initially proposed, and notes problems, solutions, and improvements found in their implementation. It also covers the ways that the improved test results helped put the case for change throughout development, and ways in which the team has since built on the initial processes to arrive at a better testing overall. |
James Lyndsay
August 2, 2002 |