Test Design

Articles

Testing the Bold and the Beautiful

During testing, testers mostly stress the 'Bold' part of the software and comfortably overlook the 'Beautiful' side. Beauty and functionality are treated as two extreme ends in software quality, where only one of the two can meet perfection at a given time. But the viewers of the famous soap opera The Bold and the Beautiful know very well that both are important. In this article, Yogita Sahoo explains why aesthetics are such an important contribution.

Yogita Sahoo's picture Yogita Sahoo
An Ingenious Solution

Is your testing tool behaving like a problem child? Injecting your application with some discipline may be what's needed. Sometimes, spending a few weeks of development time on creating a solution can save you months of testing time. In this article, Linda Hayes explains how one company did just that!

Linda Hayes's picture Linda Hayes
comparison of scripted and exploratory testing How to Choose between Exploratory and Scripted Testing

Exploratory testing has gained increased recognition as a valid testing methodology. As a test manager or engineer you may be considering which approach to take. However, just as with other aspects of testing, such as automation, its application must be carefully chosen to ensure a successful outcome. In this article we examine the factors you need to consider when making that choice.

Andrew Thompson
illustration of a generic functional testing process Reengineering Test Management

The problems due to unstructured, decentralized test management can be solved by reengineering the test management process. A testing project starts by building a test plan and proceeds to creating test cases, implementing test scripts, executing tests, and evaluating and reporting on results. This article explains the goals of reengineering test management and how to achieve them.

Prasad Patwa
the UML notation for state-transition diagrams State-Transition Diagrams

This is the fourth and last in a series of articles written to, a) introduce you to the most important diagrams used in object-oriented development (use case diagrams, sequence diagrams, class diagrams, and state-transition diagrams); b) describe the UML notation used for these diagrams; and c) give you as a tester a set of practical questions you can ask to evaluate the quality of these object-oriented diagrams.

Lee Copeland's picture Lee Copeland
Advanced SQL Injection in SQL Server Applications

This document discusses in detail the common "SQL injection" technique, as it applies to the popular Microsoft Internet Information Server/Active Server Pages/SQL Server platform. It discusses the various ways in which SQL can be "injected" into the application and addresses some of the data validation and database lockdown issues that are related to this class of attack. 

Chris Anley's picture Chris Anley
the UML for class diagrams Class Diagrams

This is the third in a series of articles written to a) introduce you to the most important diagrams used in object-oriented development (use case diagrams, sequence diagrams, class diagrams, and state-transition diagrams); b) describe the UML notation used for these diagrams; and c) give you as a tester a set of practical questions you can ask to evaluate the quality of these object-oriented diagrams.

Lee Copeland's picture Lee Copeland
example of the matrix for test cases Streamlining the Test Process

When building large test suites, one problem that crops up is test case redundancy. Test suites are especially vulnerable to this when many members of the test team are writing test cases. The likelihood of one engineer writing test cases that are somewhat covered by another engineer's is very high. This results in duplication of effort when executing the tests. I will present some strategies for avoiding this problem when constructing the test suite, as well as methods for maximizing efficiency with your test suite.

Andrew Lance
Brewing Trouble

Admit it: When you're faced with a lengthy checklist for testing, you're tempted to skip steps. Some of the items aren't really necessary, are they? They might be so obvious that there's no need to include them in the list. In this column, Elisabeth Hendrickson offers some advice on constructing useful checklists that are brief but complete.

Elisabeth Hendrickson's picture Elisabeth Hendrickson
Automated Testability Tips

Imagine a world where applications are written with automated testing in mind. Fantasy? Before you dismiss the idea, read this column. Linda Hayes makes some simple suggestions for designing for testability, including using unique names and adhering to class consistency.

Linda Hayes's picture Linda Hayes

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.