|
|
Our Experience Using Orthogonal Defect Classification Orthogonal Defect Classification (ODC) is a method of classifying and analyzing software defects. Using real-life experience, Barbara Hirsh discusses how Motorola successfully implemented ODC within their organization resulting in a framework for building a pervasive and cohesive defect prevention program. Learn the benefits of using ODC from the perspective of the developer, the tester, and the post-release analyst.
|
Barbara Hirsh, Motorola
|
|
|
A Crash Team Approach to Effective Testing Rapid changes and stunted delivery deadlines are always challenging software testers. To catch up, software testing must take a different approach without cutting corners-hence, the crash team. The crash team approach focuses on integration testing and runs in parallel with functional testing. Its technique discovers system problems early, problems that would be hard to find with traditional methods. It also supports the spiral development model that's been adopted in many rapid application development environments.
|
Pei Ma, WeiMa Group LLC
|
|
|
Adventures in Session-Based Testing 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, product sustained 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. Session-based testing can be used to introduce measurement and control to an immature test process, and can form a foundation for significant improvements in productivity and error
detection.
|
James Lyndsay, Workroom Productions
|
|
|
Testing The Chain: End-to-End Integration Test When processes include several applications, the testing process is complicated in many ways. Possible complications include: organizational issues because of the multitude of test teams and their interdependencies; processes and transactions that span the chain which require new test scenarios; integral design, information analysis, and process design documents that aren't fit for the purpose of chain testing; and test execution that demands integral knowledge of the chain. This session gives you a list of all the variables that need to be considered, then offers solutions for successfully organizing chain testing.
|
Gerard Numan, POLTEQ, B.V.
|
|
|
Applying Development Best Practices to Automated Testing Test automation is a specialized form of software development where executable code is produced for the validation and testing process. Many best practices have been identified to allow developers to code more quickly, efficiently, and correctly, but few test automators have adopted these practices. Learn about several of these "best practices"-including code reviews and coding standards-that can be applied to automated test development. Discover how you, as an automated test developer, can capitalize on the benefits provided by these practices.
|
Andy Tinkham, Spherion Technology Architects
|
|
|
Requirements-Driven Automated Testing Studies have shown that over fifty percent of software defects are attributed to poorly defined requirements. From a process improvement perspective, it is imperative that project managers establish a more effective and efficient way of defining and tracking business requirements. Jeff Tatelman describes a "how to" approach for developing a practical automated regression testing process using a traceability matrix and business event scenarios. Learn how requirements-based testing-coupled with a data-driven approach to test automation-can solve problems that plague most software development projects.
|
Jeff Tatelman, Spherion Technology Architects
|
|
|
Developing an Automated Regression Test Set Automating a regression test is a tremendous effort, but the payoff is big in situations where continuous, repeatable, repetitive testing is required. This presentation describes a real-world example of a successful team effort toward developing a reusable automated regression test set for legacy medical software products in a client/server environment. Learn the principles of team building and test case design, and the tools and utilities you need to get the job done. Patricia George also discusses how test data management, the breakdown of programming tasks, and date-driven project milestones increase efficiency to keep the team on track.
|
Patricia George, Sunquest Info Systems, Inc.
|
|
|
Implementing an Automated Regression Test Suite Many efforts to automate regression testing have failed or not met expectations-resulting in "shelfware." Lloyd Roden presents a real-world case study based on the success of implementing a regression test tool within a software company. Learn the steps taken in evaluating and deploying the tool. Discover the key benefits and successes achieved over a three-year period as well as the challenges faced while using the tool.
|
Lloyd Roden, Grove Consultants
|
|
|
STARWEST 2001: Designing an Automated Web Test Environment This paper offers an alternative to the typical automated test scripting method of "record and playback now and enhance the automation environment later." It explores a regression automation system design for testing Internet applications through the GUI, along with scripting techniques to enhance the scalability and flexibility of an automated test suite. This paper will present a basic
structure for an automated test environment, and will expand on each of the items found in that structure. Web testing levels will be laid out, along with a basic approach to designing test scripts based on those Web testing levels.
|
Dion Johnson, Pointe Technology Group, Inc.
|
|
|
STARWEST 2001: Exploratory Testing in Pairs Exploratory testing involves simultaneous activities-learning about the program and the risks associated with it, planning and conducting tests, troubleshooting, and reporting results. This highly skilled work depends on the ability of the tester to stay focused and alert. Based on a successful pilot study, Cem Kaner and James Bach discuss why two testers can be more effective working together than apart. Explore the advantages of testing in pairs, including ongoing dialogue to keep both testers alert and focused, faster and more effective troubleshooting, and an excellent opportunity for a seasoned tester to train a novice.
|
James Bach, Satisfice, Inc. and Cem Kaner, Florida Institute of Technology
|
