Application Architecture: Page

Testing for performance, part 1: Assess the problem space

In the first article of this series on testing for performance, Mike Kelly outlines ways for you to understand your content and the system and figure out where to start testing.

By Michael Kelly • Feb. 8, 2008

Prioritizing software testing on little time

Too many test cases and too little time? Expert Scott Barber explains how to prioritize testing.

Jan. 30, 2008

Testers’ involvement in requirements gathering important

In this increasingly complex software development era, it is important to include testing as early in the project as possible. And that means starting with requirements gathering.

By Adarsh Kothari • Jan. 21, 2008

Requirements gathering for payroll application

Engineering requirements for a payroll or similar application demands careful consideration. Expert Rob Apmann explains how to approach this complicated task.

Jan. 21, 2008

The state of performance testing

Some might say 2007 was the year the software industry started taking performance testing seriously. In this month's Peak Performance column, Scott Barber takes a look at what happened in the performance testing field in 2007 that made that so, and offers some predictions for 2008.

By Scott Barber • Jan. 20, 2008

Usability testing vs. user acceptance testing

Usability testing and user acceptance testing may sound similar, but these tests have different focuses and are executed at different times in the SDLC. Expert Karen N. Johnson explains how these tests work.

By Karen Johnson • Jan. 9, 2008

How to define the scope of functional security testing

With a many internal threats originating from applications, functional security testing is one of the most reliable ways to identify internal security vulnerabilities.

By Vijay Vedanabhatla • Dec. 18, 2007

Five steps for performing an effective software product review

Review or inspection is an important activity in any project implementation. Performing a good review of the developed product, along with capturing metrics, helps in building a quality product. In this member-submitted article, Murugan Srinivasa points out the significance of software metrics in guaranteeing an effective review of any software product.

By srinivasa murugan doraiswamy • Nov. 28, 2007

How to write an effective test report

This member-submitted tip provides a guideline for essential information that should be included in a test report.

By Mohamad Zakaria Alli • Nov. 26, 2007

Don’t mistake user acceptance testing for acceptance testing

Despite the many references that concur on the definition of acceptance testing, people still get confused. Scott Barber clarifies things in this month's Peak Performance column.

By Scott Barber • Nov. 20, 2007

How to create a testing scorecard

A software testing scorecard can be a good tool for managing a team's progress. Expert John Overbaugh explains how to create a testing scorecard and that fits yours and the customer's needs.

By John Overbaugh • Nov. 5, 2007

Free load and performance testing tools

What is a good choice for a free load testing tool? Expert Dan Cornell offers his advice and explains how to get started with your testing tool.

Oct. 23, 2007

Who does what in a Testing Center of Excellence?

With a Testing Center of Excellence (TCE) an organization can improve its software testing. Learn how and what each TCE participant does in this article from David W. Johnson

By David W. Johnson • Oct. 4, 2007

cruft

Cruft is the elements of a program, system or product that are either useless, poorly designed or both. In computing, cruft describes areas of redundant, improper or simply badly written code, as well as old or inferior hardware and electronics. Cruft may also be used to describe a group of hackers, like a pod of whales, exultation of larks or murder of crows. (Continued...)

By TechTarget Contributor • Sept. 27, 2007

The pros and cons of use case diagrams

Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. Kevlin Henney recommends a more balanced and restrained approach in order to not lose readers in a myriad of bubbles and microscopic text.

By Kevlin Henney • Sept. 24, 2007

How to structure a software requirements document

Effective requirements documentation is essential for any good software project. Expert Karl E. Wiegers explains how to structure your software requirements documents.

By Karl Wiegers • Sept. 19, 2007

Test plan and test strategy

Software testing is helped by a good test plans, strategies and logistics. Expert Scott Barber explains what these aspects of the testing methodology are.

Aug. 8, 2007

Software requirements specification and IEEE standards

What does the IEEE outline for requirements specifications, and how strictly should you abide by that standard? Expert Karl E. Wiegers digs into the details of an SRS.

By Karl Wiegers • Aug. 6, 2007

What to look for in a Web application security testing tool

If you do a lot of Web application security scanning, any testing tool you use must have these features, says security expert Kevin Beaver. They will save you lots of time and effort and will increase the number of valid vulnerabilities found.

By Kevin Beaver • June 23, 2007

How to test Web site login security

Input validation is critical for the security of Web sites. Here's a techniques you can use to make sure your site isn't vulnerable to SQL injection.

By Sandeep Kashyap • June 20, 2007

Software testing deliverables: From test plans to status reports

Core sets of deliverable are required for any software testing phase. In many cases they include a test plan, test case, defect documentation and status report. Learn what is required for each in this tip from David W. Johnson.

By David W. Johnson • May 14, 2007

Rewarding team members for outstanding work

Recognizing or rewarding team members for jobs well done helps build morale. Your sincere appreciation can go a long way, says project management expert David Christiansen.

April 26, 2007

How to document system, software requirements

There are various formats you can use to document system and software requirements. However, no single one is sufficient to represent all requirements. You need to follow an integrated approach.

By David Wright • April 24, 2007

The role of a software test manager

Effective software test managers not only understand the discipline of testing, but they are also able to manage and implement a testing process in their organizations. That requires team leading skills, communication skills, and being able to measure the testing team's return on investment.

By David W. Johnson • April 6, 2007

Software requirements: Using models to understand users’ needs

Successful software projects involve users early and often to explore and reach closure on requirements. Using analysis models you can depict user needs with a combination of diagrams and structure text such as tables or templated text.

By Ellen Gottesdiener • Feb. 27, 2007