Simulating a full database is a beautiful stress test, but how the heck can this be done quickly with SQL Server?

Read more »

Never look down on the bug report. With a compelling bug report, the bug report author wields tremendous influence over a software product, the team and their own reputation.

Read more »

While testing a feature that accessed the clipboard recently, I came up against an interesting clipboard scenario. What test strategies and models can we use to approach this feature in order to highlight the most important risks?

Read more »

In The Oracle Problem and the Teaching of Software Testing post, Cem Kaner wrestles with teaching how a tester could determine oracles for an exam question about automated testing. Unfortunately, the window for posting replies on the post has expired. Thus… this blog post is born!

Read more »

On Martin Anderson’s blog, he wrote a post Why QA needs to change? A few passages struck a chord with me and I considered posting a reply within the post itself. Due to the length of my response, I’ve chosen to publish a blog post instead.

Read more »

Testers are looking to assess the risk of software. So why would a tester want to test  for consequences?

Read more »

Is the purpose of testing to enforce quality, to find bugs or to automate as many test cases as possible? If the answer is yes to all three, how can all these be considered testing?

Read more »

Are you looking for a quick and dirty way to record steps, screenshots and documentation for your bug reports? Look no further than a tool that comes with Windows: Problem Steps Recorder.

Read more »