|
Functional and Regression Testing of Web Applications Gone are the days for most commercial Web sites when the "application" on the site was the Web. Now Web sites are often just the presentation layer for sophisticated applications that interact with a complexity of internal and external systems, all glued together in an elaborate architecture using Corba or DCOM. Learn how to ensure that transaction-based Web sites function properly. Explore the benefits of automated testing in these environments.
|
Peter Cook, Watchfire
|
|
STAREAST 2000: The Result of Testing Is Not Quality From this presentation's summary:
- Re-Design Testing to Provide Information to Manage Risks
- Use Risk Analysis to Determine What & When to Test (Knowledge)
- Design Test Activities to Provide Feedback about Risks (Information)
- Use a Hierarchical Test Approach with Feedback
Loops (Information+Knowledge)
- Remember The Business Goal (Wisdom)
|
Shel Seigel, Seigel Associates Corporation
|
|
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.
|
|
The Importance of the Using Right Test Techniques The choice of the right test techniques is critical to achieving a good return on the test investment. Some tests happen before we can even run the software. Some tests involve analyzing the structure of the system, while others involve analyzing the system's behavior. Each technique can involve special skills and particular participants, and might appropriately entail the use of tools-or not.
|
|
|
My Next Mission (And How You Might Benefit from It) Technical Editor Brian Marick proposes organizing a public effort to test a real software product.
|
|
|
Risk-Based Testing: How to Conduct Heuristic Risk Analysis Software testing is often motivated by risk. If you accept this premise, you might well wonder how the term "risk-based testing" is not merely redundant. However, conducting a heuristic risk analysis by employing a checklist of open-ended questions, suggestions, or guidewords is a proven approach to help you find the most important risks for developing your testing plans.
|
|
|
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
|