Mike Curn Senior SDET

Committed Senior SDET with software experience spanning manual and automated testing, development, business process improvement and release engineering. Guides teams in best practices and goals for automating repeatable processes that don’t require complex decisions and augments the management required manual operations. With a mind for easing pain points on development teams, this engineer enjoys helping teams automate builds, releases and test processes including promoting code from one environment to another.

Blogs by Mike

Selenium: Attach to an existing Chrome browser with C#

Mike CurnJuly 23, 2019August 8, 2019Leave a comment

You’re testing a desktop application with Selenium. How do you verify an item on the page after the browser launches? I recently came up against this use case and couldn’t find a clear answer for C#. Every once in a great while, the need arises to have Selenium communicate to a browser that is already […]

Painless Bug Testing through the Isolation of Variables

Mike CurnMarch 9, 2019April 4, 2019Leave a comment

Do you know why it’s crucial to catch your broken functionality before sending it to production? QA resources waste time through long, protracted test efforts that try to hammer all of their bug testing through the UI at the end of (or after) development. One of the main problems with this approach is that it […]

Deciding to Write a Wrapper

Mike CurnOctober 10, 2017October 10, 2017Leave a comment

Two things happened around the time I finished up writing a wrapper for Microsoft’s UITestControl class: I wondered if I should do the same thing for a web testing technology like Selenium, and I discovered that at least some discussions exist on if wrappers could be considered an antipattern. As I began to investigate writing […]

The Feasibility of Test Automation

Mike CurnMay 26, 2017August 7, 2017Leave a comment

With proper tools, technical approaches, and processes, automated testing improves software quality, time to market, and reduces overall costs. Starting early in the development process and maintaining a pragmatic approach will maximize chances of success. However, there is no “one size fits all” approach; proper approaches vary based on team resources and project needs. The […]

Scrum – from a QA Perspective – Part 2

Mike CurnDecember 16, 2015December 16, 2015Leave a comment

In a previous blog I talked about the benefits of being part of a scrum development team in a QA role. I also mentioned some of the pitfalls and bad habits I noticed were easy to fall into. There’s another problem, though; one originating from outside the team. That problem is one of expectations, adherence […]