<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mike C. - Senior QA Architect</title>
	<atom:link href="https://intellitect.com/blog/author/mikecurn/feed/" rel="self" type="application/rss+xml" />
	<link>https://intellitect.com/blog/author/mikecurn/</link>
	<description>Complex Software Development - Simplified</description>
	<lastBuildDate>Thu, 16 May 2024 16:31:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://intellitect.com/wp-content/uploads/2017/02/cropped-favicon-1-32x32.png</url>
	<title>Mike C. - Senior QA Architect</title>
	<link>https://intellitect.com/blog/author/mikecurn/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Don&#8217;t Write Automated Tests</title>
		<link>https://intellitect.com/blog/dont-write-automated-tests/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 21 May 2024 15:00:00 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Software Testing]]></category>
		<category><![CDATA[automated testing]]></category>
		<category><![CDATA[cost-effective testing strategies]]></category>
		<category><![CDATA[manual vs automated testing]]></category>
		<category><![CDATA[software testing efficiency]]></category>
		<category><![CDATA[testing ROI]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=59022</guid>

					<description><![CDATA[<p>Increase quality without sinking money into low-return tests A few years ago, I wrote a blog&#160;about ways to approach test automation. I touched on some considerations to help promote a successful automation project; however, I never explicitly dove into when other approaches may be better than automated tests. Specifically, I want to address an anti-pattern&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/dont-write-automated-tests/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Don&#8217;t Write Automated Tests</span></a></div>
<p>The post <a href="https://intellitect.com/blog/dont-write-automated-tests/">Don&#8217;t Write Automated Tests</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Data-Fetching from Oracle SQL Using PowerShell</title>
		<link>https://intellitect.com/blog/data-fetching-oracle-sql/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Wed, 10 Aug 2022 18:28:43 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SQL]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=54473</guid>

					<description><![CDATA[<p>Making an Oracle SQL Database and PowerShell Play Together As an SDET, my work often involves dealing with automated tests in different capacities. However, as I like to remind folks, the skillset of an SDET can extend beyond the standard expectations of knowing how to write Selenium tests. Other aspects of the role include fetching&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/data-fetching-oracle-sql/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Data-Fetching from Oracle SQL Using PowerShell</span></a></div>
<p>The post <a href="https://intellitect.com/blog/data-fetching-oracle-sql/">Data-Fetching from Oracle SQL Using PowerShell</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>A Simple Guide to Crafting Reliable Selectors</title>
		<link>https://intellitect.com/blog/a-simple-guide-to-crafting-reliable-selectors/</link>
					<comments>https://intellitect.com/blog/a-simple-guide-to-crafting-reliable-selectors/#comments</comments>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 10 May 2022 20:29:39 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=53617</guid>

					<description><![CDATA[<p>Improving Automated UI Test Reliability without Rearchitecting Your Solution Early in my automation career, a senior coworker once told me, &#34;writing automated UI (User Interface) tests is the art of crafting good selectors.&#34; By &#34;selector,&#34; I mean some methodology for finding UI elements on a webpage or application window. Standard methods are CSS Selectors and&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/a-simple-guide-to-crafting-reliable-selectors/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">A Simple Guide to Crafting Reliable Selectors</span></a></div>
<p>The post <a href="https://intellitect.com/blog/a-simple-guide-to-crafting-reliable-selectors/">A Simple Guide to Crafting Reliable Selectors</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/a-simple-guide-to-crafting-reliable-selectors/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Demystifying the SDET Unicorn</title>
		<link>https://intellitect.com/blog/demystifying-the-sdet-unicorn/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Wed, 22 Sep 2021 18:50:37 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[demystified]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=44400</guid>

					<description><![CDATA[<p>You Need an SDET Unicorn: Automation Engineers and Automated UI Tests Won&#8217;t Save You. I have a potentially controversial opinion about my job. The popular concept of the Software Development Engineer in Test (SDET) role is broken by modern development practices. I don’t say that lightly. After thirteen years in the industry and eight of&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/demystifying-the-sdet-unicorn/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Demystifying the SDET Unicorn</span></a></div>
<p>The post <a href="https://intellitect.com/blog/demystifying-the-sdet-unicorn/">Demystifying the SDET Unicorn</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Digging for Data in an Oracle SQL Database</title>
		<link>https://intellitect.com/blog/oracle-sql-database/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 30 Jun 2020 15:45:50 +0000</pubDate>
				<category><![CDATA[Data Analytics]]></category>
		<category><![CDATA[Oracle]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=37801</guid>

					<description><![CDATA[<p>How-To: Finding Columns and Tables in an Oracle SQL Database When Schema Undefined One of the great things about working at IntelliTect is we have the opportunity to get a lot of &#8220;cross-pollination&#8221; in ideas &#8211; even ideas concerning the Oracle SQL database. Recently, I was with my coworker, Chris Finlayson, and we were looking&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/oracle-sql-database/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Digging for Data in an Oracle SQL Database</span></a></div>
<p>The post <a href="https://intellitect.com/blog/oracle-sql-database/">Digging for Data in an Oracle SQL Database</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Selenium: Attach to an Existing Chrome Browser with C#</title>
		<link>https://intellitect.com/blog/selenium-chrome-csharp/</link>
					<comments>https://intellitect.com/blog/selenium-chrome-csharp/#comments</comments>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 23 Jul 2019 17:17:03 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Selenium]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=35888</guid>

					<description><![CDATA[<p>Verifying with Selenium You&#8217;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&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/selenium-chrome-csharp/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Selenium: Attach to an Existing Chrome Browser with C#</span></a></div>
<p>The post <a href="https://intellitect.com/blog/selenium-chrome-csharp/">Selenium: Attach to an Existing Chrome Browser with C#</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/selenium-chrome-csharp/feed/</wfw:commentRss>
			<slash:comments>46</slash:comments>
		
		
			</item>
		<item>
		<title>Painless Bug Testing through the Isolation of Variables</title>
		<link>https://intellitect.com/blog/bug-testing-isolation-variables/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Sat, 09 Mar 2019 15:49:29 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=34983</guid>

					<description><![CDATA[<p>Why It&#8217;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 becomes tough to&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/bug-testing-isolation-variables/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Painless Bug Testing through the Isolation of Variables</span></a></div>
<p>The post <a href="https://intellitect.com/blog/bug-testing-isolation-variables/">Painless Bug Testing through the Isolation of Variables</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Deciding to Write a Wrapper</title>
		<link>https://intellitect.com/blog/deciding-write-wrapper/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Tue, 10 Oct 2017 19:44:13 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Selenium]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=32861</guid>

					<description><![CDATA[<p>Wrappers Two things happened around the time I finished up writing a wrapper for Microsoft&#8217;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&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/deciding-write-wrapper/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Deciding to Write a Wrapper</span></a></div>
<p>The post <a href="https://intellitect.com/blog/deciding-write-wrapper/">Deciding to Write a Wrapper</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>The Feasibility of Test Automation</title>
		<link>https://intellitect.com/blog/feasibility-test-automation/</link>
					<comments>https://intellitect.com/blog/feasibility-test-automation/#comments</comments>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Fri, 26 May 2017 22:00:47 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=32231</guid>

					<description><![CDATA[<p>Test Automation 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 &#8220;one size fits all&#8221; approach; proper approaches vary based on team resources and project&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/feasibility-test-automation/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">The Feasibility of Test Automation</span></a></div>
<p>The post <a href="https://intellitect.com/blog/feasibility-test-automation/">The Feasibility of Test Automation</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/feasibility-test-automation/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Part 2: Scrum From a QA Perspective</title>
		<link>https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Thu, 17 Dec 2015 00:52:11 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=22271</guid>

					<description><![CDATA[<p>Analyzing Scrum Part 2: There is an excellent blog that describes software development as engineering a bridge: Imagine joining an engineering team. You&#8217;re excited and full of ideas, probably just out of school and a world of clean, beautiful designs, awe-inspiring in their aesthetic unity of purpose, economy, and strength. You start by meeting Mary,&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Part 2: Scrum From a QA Perspective</span></a></div>
<p>The post <a href="https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/">Part 2: Scrum From a QA Perspective</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Part 1: Scrum From a QA Perspective</title>
		<link>https://intellitect.com/blog/scrum-from-a-qa-perspective/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Thu, 06 Aug 2015 17:49:22 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=18861</guid>

					<description><![CDATA[<p>Fulfilling the Role of a QA Engineer I work QA but am not solely on a QA team; I am a member of a Scrum team. Like the other members, this means I am a part of the development team, I just happen to specialize in QA practices. This is the first position at which&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/scrum-from-a-qa-perspective/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Part 1: Scrum From a QA Perspective</span></a></div>
<p>The post <a href="https://intellitect.com/blog/scrum-from-a-qa-perspective/">Part 1: Scrum From a QA Perspective</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
