|
Every Crash, Everywhere You want to know exactly what your users in the field are experiencing. In most cases, they aren’t going to take the time to tell you. Maybe the solution is automated data collection.
|
|
|
Exhausting Your Test Options In this edition of "Bug Report," Doug Hoffman tells the story of exhaustively testing a 32-bit square root function.
|
|
|
A Look at the Perforce Version Control System Using the right tools for the job is always important; with tools that become components of your software production line, it is critical. Perforce is a version control system with ready hooks for integration into bug tracking systems. The author explains the advantages of using Perforce and why you should consider it for your team.
|
|
|
Configuration Bugs That Bite Bugs can creep in through the smallest crack. The problem may not necessarily be the testing, it might be your change management system. In this latest offering of Bug Report, the authors describe two techniques you can use on your project.
|
|
|
A Look at Test Automation with Rational's RobotJ Borrowing ideas from Robot, Rational's RobotJ focuses on automating a specific class of applications: Java and Web (HTML). RobotJ's scripts are based on a commom language (Java2), instead of yet another scripting language specific to yet another automation tool. Tom Arnold takes a look at test automation with Rational's RobotJ.
|
|
|
But It's a Feature! When you file a bug report, you become a bug advocate. It's your job to follow up to see that the bug is addressed one way or another. The way you write your report influences whether the application's behavior is changed. In this issue's "Bug Report," Danny Faught gives tips on writing successful bug reports.
|
|
|
Delivering Unwelcome News to Developers How well you present a defect to a developer can impact when a defect is resolved–or whether it is resolved at all. Deliver the information abruptly or inappropriately, and you run the risk of alienating a person or creating project hot spots that aren't needed. Deliver news too passively, and your report may be discarded. Karen Johnson describes some ways to soften the blow so that your defects are not only acknowledged, but fixed.
|
|
|
Bug Tracking Basics Effective bug tracking assures that bugs are logged, fixed, and verified by the appropriate personnel. Here's a beginner's guide to this process.
|
|
|
Defect Management with Soffront TRACK Defects Margaret Ramsey looks at Defect Management with Soffront's TRACK Defects. She concludes: "If this tool meets your requirements and its pricing isn't out of your ballpark, it's definitely worth considering. With its customizability and ease of use, TRACK Defects is one tool that should be on your evaluation list."
|
|
|
A Look at Bug Tracking Using Bugzilla Robert Sievers manages QA on the development of Abi-Word, a cross-platform free-use open source word processor. When it came time to pick a bug tracking system, he looked into Bugzilla, the open source bug tracking system created by mozilla.org, and found that the open source development model worked just as well for QA tools as it does for utilities and applications.
|
|