Application Architecture: Page

Manual testing vs. automated testing: A decision point

Automation in a test environment can be expensive and doesn’t always yield a high return. In fact, a high percentage of automation efforts fail. In this tip, Vasudeva Naidu gives advice on key factors that will lead to success in your automation initiative. Naidu describes the history of automation in test, including reasons leading to failure. Done well, and augmented by manual tests, automation can prove instrumental to a successful test effort.

By Vasudeva Naidu • Feb. 17, 2011

Waterfall vs. Agile development: A case study

Two projects very similar in scope were executed by the same project team for the same users. The first project used a waterfall methodology and resulted in missed deadlines and failure to deliver user requirements. The second used an Agile methodology, and while there were initial problems with the learning curve, the project was a resounding success. Read on to find out more about the projects, what worked and what didn't.

By Yvette Francino • Feb. 14, 2011

Agile ALM tools: How they differ from traditional lifecycle management tools

Software consultant Nari Kannan describes the differences between agile application lifecycle management (ALM) tools and traditional lifecycle management software. Agile ALM tools are more tightly integrated, easier to use, supportive to distributed teams and seamlessly integrated into many of the traditional lifecycle management functions.

By Nari Kannan • Jan. 26, 2011

Application development for mobile phones: Testing across different devices

New mobile phone models enter the market all the time, and it seems daunting to perform application testing on the various devices available. Expert Karen Johnson carefully examines the factors developers must consider and offers strategies on how to most effectively conduct application testing to ensure usability across as many mobile devices as possible.

By Karen Johnson • Jan. 11, 2011

Functional requirements and nonfunctional requirements in software engineering explained

Clearly defining both functional and nonfunctional requirements in software engineering projects is important from both a business perspective and a performance perspective. In this expert response, Sue Burk offers definitions and examples for both functional requirements and nonfunctional requirements.

By Sue Burk • Dec. 29, 2010

Eight steps for a successful software release

Have you done everything to prepare for a successful software release? Software project manager Kay Diller describes eight things you can do to ensure your deployment will go smoothly. From creating your team to being prepared with a back-out plan, Diller steps you through important considerations covering all aspects of the project.

By Kay Diller • Dec. 28, 2010

Software retest, regression, smoke and sanity testing: What’s the difference?

Understanding the nuances between different types of test efforts can be a challenge. In this expert response, Karen Johnson explains what is meant by retesting, regression testing, smoke testing and sanity testing. Find out the purpose of these types of tests and a few other terms that some organizations use for testing efforts.

By Karen Johnson • Nov. 12, 2010

Applying lean concepts to software testing

If we're going to use a factory analogy for software development, shouldn't we at least study the techniques modern factories use? In this tip, software quality expert Matt Heusser describes concepts used first for lean manufacturing, which are now being applied to software development and software testing.

By Matt Heusser • Nov. 10, 2010

What is a test case? What is a requirement?

After exploring the definition of a test case by surveying test experts, authors and students, consultant Robin Goldsmith learns that interpretations remain ambiguous and varied. Similarly, the level of detail thought to be needed to define requirements can vary and can often drive the level of detail of the test efforts.

By Robin Goldsmith • Oct. 12, 2010

Strategies for minimizing regression defects

Regression defects, those unexpected defects that result from a fix of another defect, are often the most challenging to find and fix. Expert John Overbaugh describes why these defects are so challenging and offers up techniques, such as automation and reviews, to help minimize regression defects.

By John Overbaugh • Aug. 31, 2010

Differences in Agile and traditional software project management

In this expert response, some of the differences between project management in traditional environments and agile environments are explained. One of the biggest differences is the flexibility of scope changes that is welcomed in agile environments.

By Yvette Francino • July 13, 2010

The impact of HTML5 on Web applications

HTML, the HyperText Markup Language, is an essential part of the Internet experience. HTML5 is one part of what WHATWG sees as essential to the future of Web applications.

By Bill Brogden • June 28, 2010

The importance of critical thinking in software test

Even though there are numerous definitions for the term "software testing," there is common ground. Testers need to use critical thinking skills when diving into the testing of a software application. In this tip, expert Chris McMahon explains ways for testers to increase test coverage, use proven approaches and determine which aspects of testing fit in and where.

By Chris McMahon • June 1, 2010

What does “change management” mean in software development and QA?

Change management, sometimes called configuration management, has a few different meanings in the software development community, from team changes to code changes, explains expert Yvette Francino.

By Yvette Francino • May 28, 2010

Six tours for exploratory testing the business district of your application

Exploratory testing is sometimes thought to be "directionless testing", but James Whitaker's new book suggests that exploratory testing, is more structured than it is credited for. Exploratory testing is filled with numerous tours or testing protocol, which dictate where problems might occur and where to find them and eliminate them.

By Yvette Francino • March 29, 2010

A software expert’s heuristic for regression testing

Often, regression testing is what stands between a product in a test lab versus a product in the hands of our users – so we don't want to take longer than we need – but we don't want to haphazardly release a product before its ready.

By Karen Johnson • March 16, 2010

Scrum Master or Scrum project management, is there a difference?

A Scrum Master is commonly mistaken for a project manager who works in a Scrum environment. Learn what distinguishes a Scrum Master in this expert response.

By Yvette Francino • Feb. 24, 2010

Using Fist of Five, Planning Poker to reach Agile team consensus

In these tips, consensus-building tools such as Fist of Five and Planning Poker are introduced. Even when these tools are used, the team must decide how they are going to handle a stale-mate condition and move forward on decisions.

By Yvette Francino • Feb. 17, 2010

Why use POST vs. GET to keep applications secure

Although POST and GET HTTP requests essentially perform the same command on a Web server, a security expert says there are inherent dangers in using one over the other. Learn why one type of processing request provides more security for your Web application in this expert tip.

By Kevin Beaver • Feb. 9, 2010

What are the pros and cons of centralizing a QA or software test team?

Is it better to centralize a test team or have testers paired organizationally with developers? There can be advantages to either approach. This expert response examines some considerations and an alternative that will allow your quality team to work effectively with either model.

By Yvette Francino • Feb. 1, 2010

Who determines the appropriate severity or priority for a defect?

There are often differences of opinion on the definition of severity or priority of a defect. The bottom line is determining when and if the defect will be fixed. Factors that need to be considered are customer urgency and time required to fix and test. This strategy takes into account needs of the customer, the developer and the tester.

By Yvette Francino • Feb. 1, 2010

Nine ways to evaluate automated software testing tools

Evaluate automated software testing tools more thoroughly with these tips for analyzing cost, support, total cost of ownership, usability and more. This tip suggests questions to ask about each attribute of a tool and a vendor's support for it.

By John Scarpino • Jan. 27, 2010

Problems caused by skipping analysis stage of SDLC

A requirements expert explains the possible pitfalls of skipping the analysis phase in the software life cycle development (SDLC).

By Robin Goldsmith • Oct. 5, 2009

Calculating mean time to failure in performance testing

Calculating MTTF (mean time to failure) can be a difficult for testers in order to develop a performance test pass as there are multiple steps. This expert tip will guide you through process,

By John Overbaugh • Sept. 15, 2009

Defining report requirements with use cases

This tip offers a new and interesting way to go about defining and reporting requirements for use cases. There are a number of details that need to be attended to in defining requirements such as taking a look at users and then constructing use cases.

By Betty Luedke • Sept. 10, 2009