The Latest

Most incremental releases resemble grandma's fruitcake-ad hoc pieces of customer requested functionality cobbled together in no particular order. What if, instead, you took a more structured approach—dividing your product into working layers, each one functional enough to use on a daily basis? Learn this foolproof recipe for project success.

When they receive a new software build, testers usually start their automated testing runs. Instead, what if they could execute tests automatically at the end of the build process?

As a professional test manager or test engineer, you must keep up with the latest test techniques, management practices, and systems technologies. But that is not enough.

Acceptance testing is a vital and specific form of testing whether you are tasked with rolling out an enterprise application package, releasing a major system enhancement, or developing acceptance tests in an agile development project.

Use cases are hard to test because they do not have a standard format or style, and lack coherent structure. This is due in part to the need for a standard definition in UML, which defines the graphical part but not the textual part.

Write the test. Make it green. Make it clean. This is the mantra of test-driven development (TDD).

Security issues are becoming more and more relevant as testers are called on to find security problems before others exploit them. So, where do you start, and how do you bridge the gap between honest tester and bad-guy hacker?