The Latest
|
A Look at Rational SQA Robot[magazine] Noel Nyman continues sharing his experiences of working in the Microsoft WindowsNT Group, where he evaluated several automation tools for the Applications Test team. This is the second installment in a series. |
Noel Nyman
June 26, 2002 |
|
Normal Processes[magazine] Using a sociological theory as his starting point, Technical Editor Brian Marick shows how sometimes systems can encourage local problems to blossom into system-wide catastrophes. |
Brian Marick
June 26, 2002 |
![]() |
Finding Patterns in Software[magazine] "Patterns" have caught on among software designers, especially those working on object-oriented systems. More recently, patterns have been applied to organizational behavior, including patterns for organizing independent test groups. Brian Marick provides Web resources on the study of patterns. |
Brian Marick
June 26, 2002 |
Testing and Quality: Are You As Bored As I Am?[magazine] The next time someone says to you something like, "You can't test quality into a software project," you might reply, "Well, you can't manage it in either." There may be a pregnant pause, but perhaps it will lead to thoughtful discussions about testing and quality. At the very least, it'll make those twin subjects a whole lot less (shh!) Dullsville and boring! |
Robert Glass
June 26, 2002 |
|
Finding Answers on the Net[magazine] The Internet provides a wealth of information on software quality and testing. However, finding that information can be a challenge. In this first edition of Web Watch, Brian Marick tells you how to start your search. |
Brian Marick
June 26, 2002 |
|
![]() |
Tracking Severity: Assessing and Classifying the Impact of Issues (a.k.a. Defects)[magazine] How does one categorize Severity? Should you use numbers like 1, 2, 3; generic names like High, Medium, Low; or more specific names? A telephone switching system, for example, might use industry-specific categories such as "system issue," "line issue," or "call issue." Other environments, as we'll see in this article, tailor classification terms to meet their own functional needs. |
Tim Dyes
June 26, 2002 |
![]() |
Heuristic Test Oracles[magazine] For automated testing, expected results are generated using a test oracle. Here is a look at how heuristic oracles can strike a balance between exhaustive comparison and no comparison at all. |
Douglas Hoffman
June 26, 2002 |
![]() |
How We Get More Power from Existing Tests[magazine] Richard Schooler works with the development and testing of InCert's software behavior analysis tools. In this article, Schooler describes how InCert leveraged their automated tests by thinking carefully about changes that allowed test reuse. |
Richard Schooler
June 26, 2002 |
|
A look at QARun, a GUI test automation tool[magazine] 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. |
Noel Nyman
June 26, 2002 |
Do Your Interviewing Homework[magazine] In the nerve-wracking world of job interviews, a little preparation can go a long way toward a positive experience. In this article, we'll examine some pointers for doing the research that can mean the difference between a shot in the dark and a sure thing. |
Joe Yakich
June 26, 2002 |
|
![]() |
Making the Right Choice: The Features You Need in a GUI Test Automation Tool[magazine] 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[magazine] 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. |
Bob Johnson
June 26, 2002 |
|
![]() |
Getting Automated Testing Under Control[magazine] 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). |
|
![]() |
Software Measurement Programs[magazine] A metrics program is any planned activity in which you use measurement to meet some specific goal. If you do not have a clear technical goal for a metrics program, then you are almost certainly not ready for such a program. Here's how to design a measurement program that leads to decisions and actions. |
Norman Fenton
June 26, 2002 |
![]() |
Anticipating Human Error[magazine] 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. |
Ramon M. Felciano
June 26, 2002 |