The Latest

	Testing The Chain: End-to-End Integration Test[presentation] When processes include several applications, the testing process is complicated in many ways.	Gerard Numan, POLTEQ, B.V.
	Basis Path Testing for Structural and Integration Testing[presentation] Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software.	Theresa Hunt, The Westfall Team
	The Importance of the Using Right Test Techniques[article] 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.	Rex Black July 9, 2002
	Calculating the Return on Investment of Testing[presentation] While revenues, cash flow, and earnings are vital statistics of a company's well-being, they're the by-product of what the company actually offers up as a product or service.	James Bampos, VeriTest Inc/Lionbridge Technologies and Eric Patel
	Measuring and Benchmarking IT Performance[presentation] IT leaders strive to continuously improve their software development and support practices by keeping watch on the industry's best practices.	Andy Sanchez, The David Consulting Group, Inc.
	The Guided Inspection Technique[presentation] Early detection of faults is a cost-effective technique for ensuring quality.	Melissa Russ, Korson-McGregor
	Key Risks to System Quality[article] Before we can build a high-fidelity test system, we have to understand what quality means to our customers. Test professionals can avail themselves of three powerful techniques for analyzing risks to system quality. Targeting our testing investment by increasing effort for those areas most at risk results in the highest return on investment.	Rex Black July 8, 2002
	Telling Our Story[article] Software professionals learn a lot from technical presentations and articles. But sometimes a well-told story can illustrate technical concepts even better, in an entertaining and memorable way. This week, Lee Copeland tells why it's good to be a software bard, teaching your audiences hard concepts in a decidedly nontechnical way.	Lee Copeland July 2, 2002
	Computer Science 101: Software Testing?[magazine] Summary: Where do you find new testers? For the most part, the answer is typically not "from your local university computer science or software engineering department." Testing just isn't taught as a subject in most university curricula. Here, James Whittaker suggests ways to get testing into your university.	James Whittaker June 30, 2002
	Women Testing the Waters[magazine] Picture the faces around the conference table at your last project meeting. How many women were in the room? And how many of them were testers? Alyn Wambeke explores whether the traditionally male-dominated landscape of testing is changing.	Alyn Wambeke June 30, 2002
	Generating Test Code with Teradyne TestMaster[magazine] Robin Sahner looks at generating test code with Teradyne TestMaster. His group evaluated TestMaster on two projects. It did what they hoped it would, and now they're using TestMaster on all of their projects. They're not employing it to shorten their test development time or use fewer people; instead they plan to use it to get a more complete, more easily maintained set of functional tests using the same resources. Editors Note: Teradyne SST has become a new company called Empirix.	Robin Sahner June 30, 2002
	Breaking the Language Barrier[magazine] It's wasteful, more often than not, to reinvent the wheel. Christopher Meisenzahl explains how he solved a high-tech automation challenge through the sharing of resources. When faced with similar problems, this sort of collaboration with others may be your most valuable tool—and one that every tester should take advantage of.	Christopher J. Meisenzahl June 30, 2002
	Analyzing Requirements Bugs[magazine] Analysis of bug reports from previous projects tells us about our most frequent errors, and can help us improve. But very few companies spend the time to analyze bugs from completed projects. Otto Vinter and Soren Lauesen explore using bug reports to improve the software development process.	Søren Lauesen June 30, 2002
	No More Whining[magazine] Johanna Rothman urges test managers to stop whining and deal with the "Not-Enough" problem. She concludes: "You have more capability to influence attitudes, behaviors, and actions in your organization than you know. If you feel like a second-class citizen, reframe the situation. Rethink your job and how you do it, and realize the importance of the contribution–finite, but powerful–you can make toward your organization's product quality."	Johanna Rothman June 30, 2002
	Flying Solo: Is Consulting for You?[magazine] Alyn Wambeke interviews several software consultants for their take on the ups and downs of working on their own. He also gives pointers on getting started, and on how to determine if you're up to the challenge.	Alyn Wambeke June 30, 2002

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.