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.
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?
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!
In September, I posted about how to pre-process the captured content to maximize successful optical character recognition (OCR) . In this post, we’ll use ABBYY FineReader for optical character recognition (OCR) to produce an eBook.
I got an SMS a few days ago with a Get media content now hyperlink. Here’s how to view it.
Tired of paying for Kindle ebooks? Here’s how you can make your own!
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?