1. My Tests Are Killing Me

Since the early days of Extreme Programming, tests have been touted as “executable documentation”. In practice, however, many tests fail to live up to that ideal and worse become a time sink when trying to decipher test failures.

Using examples and focusing specifically on unit or developer tests, this recorded presentation examines the characteristics of readability in tests and offers advice on making your tests more readable.

Watch the complete talk here.

, , ,

1. Using Games to Make You a Better Tester

Though the word “games” may not elicit the same response today as it did when we were children, you have to admit…games are always exciting (even if they’re designed for so much more than fun).

For example, in the software testing world, there are tester games. These kinds of games are focused on testing skills and can show you how the other members of your team think, make you think about how you think, and even help you change the way you approach testing.

, , , ,

Imagine this nightmarish scenario:

A sizeable crash has just happened, and your company website has stopped functioning. It’s a big deal, and you’re certainly feeling anxious due to the loss of both revenue and reputation, but more surprises may lie in the aftermath. Any company that has experienced a catastrophic crash knows that it’s like an earthquake. The same problems can strike more than once, just like aftershocks, shaking you off your feet just when you’re beginning to regain confidence.

, , ,

1. Destructive Software Testing

So what exactly is destructive software testing? It’s the method of identifying the point of an application’s failure. Though this sounds like regular functional testing, the author asserts that there is, in fact, a bit more to destructive software testing.

In contrast to conventional testing that determines if an application can perform its functions correctly, destructive testing is meant to account for unpredictable user behavior within your application.

, , ,

1. What Keeps Me in Software Testing

After eleven years in the software testing industry, it’s no wonder that author Matthew Heusser decided to write a post explaining why he’s stuck around. From bug hunting to determining core business drivers to delivering a better product, Matthew’s reasons may even remind you of some of your own.

He concludes his article with lessons learned – a valuable read for testers at any level.

Take a look!

, , , ,