The Latest

Taking development and business contexts into consideration can mean the difference between a correct assessment and a useful assessment. Here's information on how to provide an assessment that's both correct and effective.

A major challenge for software professionals interpreting data is deciding what's real and what isn't, what matters and what doesn't. A useful way to think about it is that you are trying to find the signal in the noise produced by random variation and error. Here is advice on how to extract the useful information from the "noise."

Appreciating differences is critical for productive teams. Different approaches aid in finding solutions, and mutual respect dramatically improves group problem solving. Testers should not be judged according to developer criteria.

The explosion of personal information on the Web has made privacy a primary concern. Here are pointers on making sure your site works for security-conscious users, as well as information to help you avoid inadvertent compromises of privacy.

Test coverage is about insuring that test plans and test cases include information vital for successful testing of the program in the areas of functionality, performance, and the overall quality of the software. This article shows how to create a plan of attack to provide strong test coverage, determine the scenarios for the test plan, and manage the changes made to information used by testing.

The assumptions you make about the people you manage can shape your management style. Here's a detailed look at three distinct styles of management and how they apply to your software projects.

Monkey testing refers to automated testing done randomly without any "typical user" bias. Here's a look at how to use such random testing techniques to cost-effectively catch bugs you might otherwise miss.