The Latest

Analysis and testing for data warehouse and business intelligence (BI) projects typically confirm that data was correctly mapped and can be accessed as intended. Such work is absolutely necessary, though not sufficient.

What if there were a way that testers could practice the craft of testing and learn from mentors all over the world? A way they could tackle interesting problems with both novices and experienced testers participating together?

Do you ever get that creeping feeling there is more to agile testing than automating it? Have you wondered how you should test quality considerations beyond the story cards?

Structured test design techniques have been around almost as long as testing itself. Some people even call them old school and out-of-date.

The best software development teams find ways for programmers and testers to work closely together. These teams recognize that programmers and testers each bring their own unique strengths and perspectives to the project.

On agile teams, testing is an ongoing activity-not a phase or a role. Even today many agile development teams struggle with this concept.

An efficient test finds the most important defects as early as possible and at the lowest possible cost. The challenge for many of us is determining which tests are most important to execute and when to perform them.