Author

Paul Merrill

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 Updated (6/26/17) – Clarified how much manual is “required” for test automation. 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 […]

Allocating Automation Engineers Time

Allocating Automation Engineers Time Update (6/26/17): I’ve updated to clarify amount of manual testing I’m referring to. Update (10/17/16): 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 […]

Transitioning from Manual Testing to Automated Testing

The Journey – Transitioning to Automated Testing I love working with teams to transition from manual testing to automated testing. One of my favorite things is walking with teams in that journey and helping shine a light out in front of them. If you don’t know the path or can’t see […]

An Uncomfortable Truth

An Uncomfortable Truth Several months ago I started writing down my beliefs about testing. One of those beliefs was: My customers are: Developers, Product Owners, my clients’ Customers, Management, Operations, and other Testers. Another was: The most important thing I can do is give accurate, clear, fast, and concise information […]

Risk Assessment

My clients –Product Owners– have the right to determine acceptable level of risk for the application Who else would? How often, as testers, do we find ourselves arguing adamantly about a certain test or piece of functionality? It needs more testing. I don’t think it works. Why can’t we spend more […]

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 […]

Broken Builds

What rules does your team have about broken builds? How long do you allow a build to remain broken? Who fixes it? Who determines why a test failed? What options exist for a broken test? Do you identify and fix immediately? Does the team allow ignored tests? Should you fess up to the team when […]

What I Believe About Testing

Recently, I found it necessary to enumerate my beliefs about testing. I thought it would be good to share them with you. I’m sure these will change over time, as they have changed to this point. I’d like to know your thoughts in the comments. Enjoy. ~Paul What I believe […]