|
Testing Windows Registry Entries Warning: Registry keys may be hazardous to your program's health! Registry key entries in Windows applications-visible or hidden-are often neglected by testers. A registry key entry is a program feature just like any other application function and as such needs to be validated. Michael Stahl describes why registry keys should be accorded special attention during testing and proposes a strategy for mitigating risks posed by incorrect registry key entries. He suggests a test strategy, as well as coding standards for input value and type validation, default values, regeneration, and naming rules. Michael demonstrates the use of correct and incorrect registry keys in common commercial applications.
|
Michael Stahl, Intel Corporation
|
|
Deploy a Peerless Peer Review Process Peer review programs are like parachutes-proper deployment is essential; otherwise, they inevitably will crash. When effectively implemented, peer reviews have a significant return on investment and result in greater product reliability. Lee Sheiner shares the key features for making peer reviews a value-added practice at Georgia Tech Research Institute, including: selecting the proper type of review for each work product, identifying the right reviewers, focusing on early defect detection, using supporting tools, fostering an environment conducive to reviews, managing the review materials, and much more. Learn from Lee the ways they have crosspollinated peer review methods across the organization and how successful peer reviews encourage project groups to "gel" and become highly productive teams.
|
Lee Sheiner, Georgia Tech Research Institute
|
|
The Value-added Manager: Five Pragmatic Practices What do great managers do that others don't? Great managers focus their efforts, increase their productivity, and develop their people. In this session, Esther Derby describes five pragmatic practices that managers can apply to improve both work results and worker satisfaction-give both positive and corrective feedback weekly, consciously decide what not to do, limit multitasking, develop people, and meet with staff individually and as a group every week. Esther says these ideas are not rocket science. If you apply these five practices consistently you will improve the value of your team to the organization-and keep your sanity, too.
|
Esther Derby, Esther Derby Associates Inc
|
|
STARWEST 2005: Testing Outside the Bachs: A Hands-On Exploratory Testing Workshop Simply put, exploratory testing means designing your tests as you perform them. When it's done well, it's a fantastically productive and rewarding approach to testing. However, to do it well requires training, practice, and discipline. Lecture presentations about exploratory testing are a poor substitute for seeing it and doing it. So ... plan to bring your laptop to this session and test along with James Bach and Jon Bach as they demonstrate exploratory testing in a live testing workshop. Participate or just observe as exploratory testing is performed in real time with play-by-play and color commentary. Learn how to bring structure to this apparently unstructured testing method. See if you can find bugs that they do not find as you test "outside the Bachs"!
|
Jon Bach, Quardev Laboratories
|
|
Test Driven Development - It's Not Just for Unit Testing Test-driven development (TDD) is a new approach for software construction in which developers write automated unit tests before writing the code. These automated tests are always rerun after any codes changes. Proponents assert that TDD delivers software that is easier to maintain and of higher quality than using traditional development approaches. Based on experiences gained from real-world projects employing TDD, Peter Zimmerer shares his view of TDD's advantages and disadvantages and how the TDD concept can be extended to all levels of testing. Learn how to use TDD practices that support preventive testing throughout development and result in new levels of cooperation between developers and testers. Take away practical approaches and hints for introducing and practicing test-driven development in your organization.
|
Peter Zimmerer, Siemens
|
|
Systematic Techniques for Fault Detection and Isolation Selecting the appropriate testing techniques and test cases improves test efficiency, reduces time to market, and gives you confidence that the system is ready to ship. Using real-world case studies as examples, Madhav Phadke explains the fundamentals of robust test case selection and how code coverage can improve your test results. He discusses ways for testers to support debugging and faster repairs by isolating defects to a specific part of the software. Learn to select test outputs based on "total function evaluation" rather than end customer outputs and ways to use orthogonal arrays for testing combinations of parameters. Take away a list of free or inexpensive tools that can speed up your testing process.
|
Madhav Phadke, Phadke Associates
|
|
How Much Building Is Too Much? Staged integration versus continuous integration—which does your team prefer? Can't decide if one is better than the other? In this column, Johanna Rothman explains that you can create the perfect blend of the two. Developers and testers benefit from frequent builds, but be careful with how much you build. Build too much or too little and a project could topple.
|
|
|
Changing Minds About Context Switching Turn to The Last Word, where software professionals who care about quality give you their opinions on hot topics. This month, Johanna Rothman explains what technicians can do to convince management that context switching in the technical world is a sure-fire means to a late project.
|
|
|
The Short Management Lifecycle Every manager has a story to tell. Find out how one management professional tackles a fictional dilemma. The story may be made up, but the solutions are tried and true. In this installment, Patrick Bailey tells the harrowing tale of a skilled technician-turned-manager who finds himself in a sticky situation with his CEO.
|
|
|
The Good, the Bad, and the Agile Customer What do you do when assigned the role of project customer, with a team that has never worked with a customer, building an application that was barely thought out? Sound like a nightmare? It doesn't have to be. Find out how one project manager beat the odds to produce a high-quality, on-time release.
|
|