Nuts and Bolts

Archives

Differing Priorities for Continuous Integration

During a recent webinar on Continuous Integration (CI), I talked about the concerns of developers vs the concerns of testers in relation to CI (sign up to never miss another webinar here). The pressures developers face are different from those faced by testers. In this post I name a few […]

Why Offer TDD in Java? – Reason #1

Why are we offering Test Driven Development in Java starting February 27? This week I’ll post 3 reasons (read Reason #2 & Reason #3)… Reason #1: Better test automation engineers One of my goals is to push the discipline of test automation forward. To do this, I like to help test automation engineers grow. […]

Mailbag: When an Automation Engineer is Better than Devs

Are Test Automation Engineers who are better coders in the wrong place? After posting “7 Ways to Better Automation”. I received the following question about Test Automation Engineers who are better coders: If your tester can write test code better than product code that’s catch-all-error, more robust and consistent, I think he’s […]

My Introduction to Continuous Integration

My Introduction to Continuous Integration My introduction to Continuous Integration came in 2002. The first day of my work for a retail company, I walked in & we immediately discussed tasks. Then we estimated them, paired up, sat down and started working. At the desk was one keyboard, one mouse, […]

Should You Write Automated Tests for Your Automated Tests?

Should You Write Automated Tests for your Automated Tests? Recently, I posted 7 Ways to Better Test Automation on a few linkedin groups. The response was overwhelming. I appreciate all the comments, thoughts and other ideas. Several of the comments deserved more than a reply on linkedin, however. Over the […]

7 Ways to Better Test Automation

7 Ways to Better Test Automation 1) Test it By a wide margin, testers produce the most defect-prone code I see. Make sure to test your test code. Shouldn’t test code be the best code? It’s responsible for alerting us to whether other code is correct, so it must be […]

Clarifying the Role of Test Automation Engineer

The Role of Test Automation Engineer I’ve been made aware of assumptions I made in my last post about allocating automation engineers’ time. Please read that before reading this. We all function on assumptions everyday at one level or another, but that doesn’t mean the ones I made shouldn’t be […]

Allocating Automation Engineers Time

Allocating Automation Engineers Time Update (10/17): I’ve clarified some of the terminology here in a new post. People want to believe automation engineers are not software engineers. But, the same skills and environment that are needed for software engineering are needed for test automation. Automation Engineers need uninterrupted, consistent time […]

Free Webinars on Automated Testing!

New Free Webinars – Automated Testing Check out our upcoming and past webinars over on the webinars page. Sign up for the next one. We’ll be talking about what to automate first. There are a lot of different thoughts about this, but we’ll tell you what works and what doesn’t during […]

100% Code Coverage

100% code coverage? Why not? In a recent post entitled “What I Believe About Testing” I wrote “It is rare that 100% code coverage is necessary”. This may have caught people off guard — that a test professional doesn’t believe in 100% code coverage. Understand why… Cost vs Benefit I’m […]