|
The Future of Code Coverage Tools Modern optimizing compilers are becoming increasingly dependent on dynamic profile information. Because the profile information collected by these compilers also is sufficient for QA, it is likely that code-coverage analysis will become an integrated development environment option. This integration should help to simplify your code development and testing processes and should also improve the accuracy of your coverage information and the performance of your optimized code.
|
|
|
The Best Testers are Free Beta programs and early release programs are commonly used in software release cycles. The next level of partnership is bringing actual customers into the test lab. When customers test, even for short periods of time, their contribution can change your test practices and test environments forever. The best part is, they’ll do it for free! Learn how to recruit customers for testing and then use them to improve test practices within your test team.
|
Adam Tate, IBM Corporation
|
|
.Net-A Complete Development Cycle This article discusses the software development practices that were used before the inception of .NET detailing which ones worked and which ones didn't. The .NET development lifecycle and how to implement it for your team is also explained.
|
Gunther Lenz, Siemens Corporate Research
|
|
Leading Successful Software Projects Presentation Leading Successful Software Projects
|
Andy Kaufman, Institute for Leadership Excellence and Development
|
|
STAREAST 2003: Rapid Web Testing in a High-Velocity Environment This paper discusses implementing METS (Minimal Essential Testing Strategy) for your test team. METS is a strategy to help get the essential testing for your project done within the time frame allowed. Step by step instructions for using this methodology are included.
|
Greg Paskal, Kinko's
|
|
eXtreme Programming's Unit Test Fixtures: Experience from the Field Are you interested in adopting eXtreme Programming's (XP) unit test fixtures and related methods? Stan Bell shares his team's experiences with the Visual Basic version of the Xunit unit test framework. He then explains the methodology employed in the development shop, i.e., how engineers and QA analysts interacted prior to the application of this technique versus after. He points out the challenges, pitfalls, and successes encountered during the adoption process, and reports on the much-improved defect detection and correction rates that occurred post-adoption.
|
Stan Bell, McKesson
|
|
Effective Testing for Java-based Web Software This presentation addresses the following: What is Java software, anyhow? How do you test Java? How do you build testable Java applets/applications?
|
Sam Guckenheimer, Rational Software
|
|
Software Inspection: Taking a Step Forward to Completion n
|
Neela Majumder, Intel Corporation
|
|
Analyzing Web Application Errors This presentation focuses on the characteristics of Web application errors to derive key issues to consider in analyzing and reproducing errors. Learn how to isolate application errors from configuration and technical support issues. Explore effective techniques to make errors reproducible. Examples of common and uncommon Web application error types are provided.
|
Hung Nguyen, LogiGear Corporation
|
|
Does Test Length Matter? According to popular testing folklore, long tests are more likely to find bugs than short ones. Based on a series of experiments using formal traversal tools, Shmuel Ur demonstrates that long tests do indeed achieve better coverage and are lower in costs than test suites built of short tests. Explore the trade-offs between short and long tests while learning the effective strategies of converting test requirements to test plans.
|
Shmuel Ur, IBM Research
|