|
A look at QARun, a GUI test automation tool QACenter provides an integrated solution that will help you test GUI applications and track the bugs you find. As with most tool suites, you get the best results if you use all the features. If you don't need some parts of QACenter, the integration is less important to you. Then the strengths and weaknesses of the individual tools, like QARun, are more significant.
|
|
|
Getting Automated Testing Under Control The authors have overcome a lot of the roadblocks to systems testing, especially automated testing. In this article they present their ideas and techniques that are easy to implement (for example, test clusters, templates, and navigation methods).
|
|
|
Making the Right Choice: The Features You Need in a GUI Test Automation Tool GUI (graphical user interface) tools can boast a lot of capabilities. Approaching GUI test automation as a programming project, you'll need a tool appropriate to the size of your project. Here's a rundown of the key features you'll need in the GUI test automation product you buy.
|
|
|
How to Ensure that Your Configuration Management System will Function Fully and Correctly No matter what the origin of your CM software, improper installation, poor training, and program defects can lead to disaster. This article discusses how to make the most of your current CM tools, and how to ensure that your CM system will do what it's supposed to do.
|
|
|
It's January 1, 2000 . . . What Have You Overlooked? You have a Y2K effort in place, and it's all about preparation for an event you know is coming. What have you overlooked that’s going to bite you? This article will help give you 20-20 foresight to anticipate potential "gotchas."
|
|
|
Anticipating Human Error This article makes three points. First, errors happen. Second, systems can encourage errors. Third, a basic understanding of the kinds of errors humans make can help us design better systems. Here are some suggestions to help avert trouble.
|
|
|
Web Load Test Planning Predicting how a particular Web site will respond to a specific load is a real challenge. Here are three basic steps necessary to design highly realistic and accurate Web site load tests.
|
|
|
Reporting Systems: Tracking the Details If you're paying the bill for all the graphics, glitz, and applets, you're going to want to have some evidence that thousands of potential customers have actually seen your Web site. Here is a step-by-step recipe for testing system, network, and Internet reporting systems.
|
|
|
Adventures in Automated Testing Sometimes the best teacher is experience. Here's a look at four real-life projects, each with a different problem domain, testing approach, and test tool, and the lessons they offered in automatic test generation.
|
|
|
Test Design: Developing Test Cases from Use Cases A use case is a sequence of actions performed by a system, which combined together produce a result of value to a system user. Use cases describe the "process flows" through a system based on its actual likely use, so the test cases derived from use cases are most useful in uncovering defects in the process flows during real-world use of the system. Here is an example of how a use case is used to derive and prioritize test cases.
|
|