Dedicated 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 and increasing efficiency of manual processes. With a mind for easing pain points on development teams, this engineer takes advantage of current technology including Azure Boards, Azure Pipelines, Test Plans and Azure VMs to helping teams maximize productivity.
Blogs by Mike
How to find columns and tables in an Oracle SQL Database when you don’t know the schema. One of the great things about working at IntelliTect is we have the opportunity to get a lot of “cross-pollination” in ideas – even ideas concerning the Oracle SQL database. Recently, I was with my coworker, Chris Finlayson, […]
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 […]
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 […]
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 […]
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 […]