|
|
Testing your Web Site for Privacy, Quality, and Accesibility Today's business world relies heavily on transactions conducted through the web. Because of this, brand image and how a web site is rendered to customers has become increasingly important. A poorly functioning web site poses significant risk for web-based companies. This presentation discusses the challenges involved when testing to ensure the quality of your company's web site and to ensure that the components of the site function properly. With the ever-increasing web complexity, specific tools and processes are required to manage these challenges.
- Discover ways to ensure that your web site reflects your privacy policy
- Learn how to manage your web sites's links to ensure that they remain current and unbroken, and ensure that web content is accessible to users
- Learn about specific tools and processes to test and manage your web site
|
John Burg, IBM Global Services
|
|
|
Fault Injection to Stress Test Windows Applications Testing an application's robustness and tolerance for failures in its natural environment can be difficult or impossible. Developers and testers buy tool suites to simulate load, write programs that fill memory, and create large files on disk, all to determine the behavior of their application under test in a hostile and unpredictable environment. Herbert Thompson describes and demonstrates new, cutting edge methods for simulating stress that are more efficient and reliable than current industry practices. Using Windows Media Player and Winamp as examples, he demonstrates how new methods of fault injection can be used to simulate stress on Windows applications.
- Runtime fault injection as a testing and assessment tool
- Cutting edge stress-testing techniques
- An in-depth case study on runtime fault injection
|
Herbert Thompson, Security Innovation
|
|
|
Creating an Error-Prevention Culture Error prevention refocuses development teams from testing
for and fixing bugs, to improving the software development process enabling the delivery of higher quality software. This article explains the importance of implementing the right error prevention solutions.
|
Gary Brunell, ParaSoft
|
|
|
Damage Prevented: The Value of Testing Techniques to help your software team prevent defects in projects are detailed. This article also discusses the economic value of testing.
|
Tim Koomen, Sogeti
|
|
|
Defect Escape Analysis for Test Process Improvement An escape is a defect that was not found by, or one that escaped from, the test team. Implementing the escape analysis method for test improvement can increase the quality of software by lessening the occurrence of software defects.
|
Mary Vandermark, IBM Corporation
|
|
|
Bug Taxonomies: How to Generate Better Tests This article discusses how to use bug taxonomies to help generate better tests. The author explains that a test team's goal should be to create a useful taxonomy that can be used as a framework to brainstorm for possible risks to the application.
|
Giri Vijayaraghavan, Texas Instruments Inc
|
|
|
STAREAST 2003: How to Break Software This course will provide you with some ideas to make your testing more effective. These ideas require self-study, practice, practice, and more practice. Take a look inside as James Whittaker teaches you how to break software.
|
James Whittaker, Florida Institute of Technology
|
|
|
STARWEST 2002: Writing Better Defect Reports Why is it that some testers get better responses from developers than others? Part of the answer lies in their defect reports. Following a few simple guidelines can smooth the way for a much more productive environment. That's because the objective shouldn't be to write the perfect defect report, but to write an effective defect report that conveys the proper message, gets the job done, and simplifies the process for everyone. It's important that you use this report to ask and answer the right questions. Kelly Whitmill gives you a quick mental inspection checklist you can reference each time you write a defect report. You'll walk away with information that can make a significant difference the day you get back to work, on a topic that's often overlooked in the industry.
|
Kelly Whitmill, IBM
|
|
|
Applying Orthogonal Defect Classification Principles to Software Testing Test escape analysis and corrective action tracking (TEACAT) is a method used to collect and utilize information about the causes of test escapes to prevent customer-found defects and improve internal test, development, and release processes. The TEACAT approach provides testers and test managers with the primary causes of defect escapes from the organizations into the field. Suzanne Garner takes you through the test escape analysis process at Cisco and shows you how test-specific ODC fields can be employed to provide customer focus to test process improvement activities, and ensure that test gaps are closed.
|
Suzanne Garner, Cisco Systems Inc
|
|
|
How to Write Better Test Cases Test cases are the biggest investment and greatest asset of a software quality team. Dianne Runnels explains practical methods to maximize the return on this investment through clever strategies and writing techniques. Learn how to make cases easy to test, increase productivity, and respond to project changes.
|
Dianne Runnels, Interim Technology Consulting
|
