<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on pavsaund.com</title><link>https://www.pavsaund.com/tags/testing/</link><description>Recent content in Testing on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 26 Oct 2014 18:00:21 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>The boy scout rule</title><link>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</link><pubDate>Sun, 26 Oct 2014 18:00:21 +0000</pubDate><guid>https://www.pavsaund.com/2014/10/26/the-boy-scout-rule/</guid><description>&lt;p&gt;Recently I had the discussion with a colleague on how new code was being added to a code-base without maintainability in mind. The discussion was sparked by a code-review that had been ping-ponging between the reviewer and the developer where readability and ( as a result ) maintainability was an issue.&lt;/p&gt;</description></item><item><title>Acceptance driven bugfixing</title><link>https://www.pavsaund.com/2014/10/26/acceptance-driven-bugfixing/</link><pubDate>Sun, 26 Oct 2014 16:56:31 +0000</pubDate><guid>https://www.pavsaund.com/2014/10/26/acceptance-driven-bugfixing/</guid><description>&lt;p&gt;&lt;em&gt;I originally posted this on &lt;a title=&#34;Acceptance driven bugfixing&#34; href=&#34;http://blog.dolittle.com/2013/06/04/acceptance-driven-bugfixing/&#34;&gt;the dolittle blog&lt;/a&gt;&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;There&amp;rsquo;s a new task waiting for you in your inbox&amp;hellip; a &lt;strong&gt;bug&lt;/strong&gt; in production! Maybe the bug is completely unrelated to  code, you&amp;rsquo;ve created, but the report is there waiting for you. It&amp;rsquo;s critical, and has to be fixed &amp;ldquo;today&amp;rdquo; or &amp;ldquo;ASAP&amp;rdquo;! And with a number of consequences, like &amp;ldquo;this feature is vital!&amp;rdquo;, &amp;ldquo;support center is being called down by angry customers&amp;rdquo;, &amp;ldquo;we&amp;rsquo;re losing millions!&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Interactive jQuery tester</title><link>https://www.pavsaund.com/2010/10/22/interactive-jquery-tester/</link><pubDate>Fri, 22 Oct 2010 23:12:55 +0000</pubDate><guid>https://www.pavsaund.com/2010/10/22/interactive-jquery-tester/</guid><description>Interactive jQuery tester I dug this link up the other day, and thought I&amp;rsquo;d spread the love :)
If you&amp;rsquo;ve ever had debugging issues with your jQuery selectors. Or would like to experiment a bit then the Interactive jQuery tester is a great solution. You paste your HTML, then type in the selectors. The elements that are actually selected are then highlighted, which gives instant feedback.
Hope you find this as useful as I have in the past.</description></item></channel></rss>