|
A Look at Mercury Interactive's WinRunner In this edition of "Tool Look," Chris Meisezahl takes a look at Mercury Interactive's WinRunner.
|
|
|
A Rush to Judgement If you find an article grating on you, if you think the author is clearly wrong-headed, I suggest you read it differently than you probably read most articles. Explicitly separate what the author implies you should believe from the actions she describes. Focus on her specific results and the actions that led to them. How, in your style of work could you adapt the author's actions to get your results? In this edition of Technically Speaking, Brian Marick explores this possibilty.
|
|
|
Eliminating Automation Overhead Overhead code is code that is necessary for carrying out the operations of an automated test, but obscures the test's point. Find out how using interface layers can lead to greater efficiency and easier maintenance.
|
|
|
Orchestrating Integration Testing Verifying the operation of a complex software system can be a daunting task. Here is a systematic approach to the job. This article details six steps for testing duct-taped programs.
|
|
|
Leveraging Inspections You can improve your inspection process, moving from 50 percent to as much as 90 percent defect removal before entering test. Learn how to record and analyze the right data.
|
|
|
Testing the Programs That Test Programs This edition warns of the trouble that comes when you start testing the programs that test programs. Next-generation tools could be just what your project needs. Linda Hayes explains the pros and cons of implementing such a solution.
|
|
|
The Care and Feeding of Testing Skills It's a good idea to thoroughly study the bugs that have already been found in the software you're testing. It's even better if you study other people's bugs, too. Read on in this issue of Career Development as Elisabeth Hendrickson provides a helpful guide to continuous professional development.
|
|
|
Security Testing by Steven Splaine For anyone involved in security testing, or for anyone who is just plain curious about this area of software testing, the following references will provide a good starting point for any effort that you might be asked to undertake. In this issue, Steven Splaine discusses this important aspect of software engineering.
|
|
|
Troubleshooting Risk-Based Testing It's not easy to know the ways that a product might fail, determine how important the failures would be if they occurred, and then develop and excuse tests to discover whether or not the product would indeed fail in those ways. Renowned tester James Bach shares some of his tips for dealing with common risk-based testing obstacles.
|
|
|
Taking Test-Driven Development for a Drive Sometimes TDD (Test-Driven Development) doesn't get used because it can be cost prohibitive to a testing budget. Read on as Joel Spolsky laments the limited real-life usefulness of test-driven development and discusses some common roadblocks to using this testing technique.
|
|