|
Testing Without a Map When faced with the task of testing an unfamiliar application, it's sometimes difficult to know where to begin. Discover how exploring with heuristics in mind can help you uncover bugs—even when you don't know what the system specifications are.
|
|
|
A Killer Bug for the New Millenium We're pleased to bring you technical editors who are well respected in their fields. Get their take on everything that relates to the industry, technically speaking. In this issue, find out why our guest editor thinks he's found the bug that will once again bring testers to the forefront—a bug that dwarfs Y2K and could put big, rich software companies out of business.
|
|
|
Don't Just Break Software. Make Software What if, instead of using tests to try to break software, we used tests to make software? That's the vision of storytest-driven development. We spoke to people who spend each day turning wishful thinking into working products. Find out how they do it.
|
|
|
Logical Capture/Replay Wouldn’t it be great if test scripts were written in terms of what they were trying to accomplish instead of in terms of which button to click? It would certainly make them a lot less fragile, and much easier to understand. Find out how capture/replay at the business and control logic level can help you accomplish this goal.
|
|
|
Make It Personal Often, despite all the data, the bugs, and the business case for quality, people don't make real changes until they discover what's in it for them. Bob Lee shows you how to make quality matter to those upstream.
|
|
|
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.
|
|
|
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.
|
|
|
Action Figures Models can be invaluable testing tools. Unfortunately, they are often difficult to automate. One solution is to have testers use action words, or action-based testing, to express models. This enables them to design action-based models that can be easily automated by a programming expert. Let Hans Buwalda teach you how to employ action words to help you get the job done.
|
|
|
Usability and Privacy While most bugs that make headline news are due to careless software implementations exploited by skilled hackers, the problems in KaZaA center around its user interface. This article details KaZaA's application flaws and then suggests ways to prevent such flaws.
|
|
|
Deconstructing GUI Test Automation Window mapping gives elements specific names so tests are easier to update and understand. Task libraries group sequences of steps that make up part of user tasks when those sequences show up in multiple tests. Data-driven test automation separates the parameters of a test case from the test script so that the test script can be reused for many related tasks. Keyword-driven test automation formats tests as tables or spreadsheets and creates parsers to read and execute the test descriptions. Take advantage of these four techniques to help you test a graphical user interface, and see how developers can make your life easier.
|
|