<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jpcody)</title>
    <link>https://pinboard.in/u:jpcody/public/</link>
    <description>recent bookmarks from jpcody</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://chancejs.com/#true-random"/>
	<rdf:li rdf:resource="http://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html"/>
	<rdf:li rdf:resource="http://arjanvandergaag.nl/blog/factory_girl_tips.html"/>
	<rdf:li rdf:resource="http://michelf.com/projects/multi-safari/"/>
	<rdf:li rdf:resource="http://zombie.labnotes.org/"/>
	<rdf:li rdf:resource="https://github.com/andyedinborough/stress-css"/>
	<rdf:li rdf:resource="http://httpstat.us/"/>
	<rdf:li rdf:resource="http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript"/>
	<rdf:li rdf:resource="http://tester.jonasjohn.de/"/>
	<rdf:li rdf:resource="http://esbueno.noahstokes.com/post/104048692/3-step-process-for-troubleshooting-your-css-step-1"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://chancejs.com/#true-random">
    <title>Chance.js: Utility library to generate anything random for JavaScript</title>
    <dc:date>2013-06-25T03:06:15+00:00</dc:date>
    <link>http://chancejs.com/#true-random</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Chance is a minimalist generator of random [1] strings, numbers, etc. to help reduce some monotony particularly while writing automated tests.

]]></description>
<dc:subject>javascript testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5ac05547687b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html">
    <title>Don't Make Your Code &quot;More Testable&quot;</title>
    <dc:date>2012-07-16T15:37:47+00:00</dc:date>
    <link>http://gmoeck.github.com/2012/07/09/dont-make-your-code-more-testable.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In some ways I'm very excited that the Ruby community seems to have taken up the "Mocking/OO flag" so to speak lately. Most of the Ruby conferences seem to have talks around "Object Oriented Rails", "Isolated Unit Tests", and things like the "SOLID Design Principles". And even more exciting for me is that I see more and more people referencing the Growing Object Oriented Software Guided By Tests book. I think these are all great steps for us towards producing more maintainable software over time.

]]></description>
<dc:subject>ruby testing tdd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:48c8ffccfd9c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:tdd"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arjanvandergaag.nl/blog/factory_girl_tips.html">
    <title>FactoryGirl Tips and Tricks by Arjan van der Gaag</title>
    <dc:date>2012-07-03T18:48:20+00:00</dc:date>
    <link>http://arjanvandergaag.nl/blog/factory_girl_tips.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[FactoryGirl is an awesome fixture replacement library that gives you a lot of power and flexibility, at the cost of more code to maintain and increased mental overhead. It pays get to know it, so you can wield its flexibility to improve your tests and your productivity.

]]></description>
<dc:subject>rails testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:980fefd7c8ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://michelf.com/projects/multi-safari/">
    <title>Multi-Safari</title>
    <dc:date>2012-01-04T16:52:05+00:00</dc:date>
    <link>http://michelf.com/projects/multi-safari/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Safari normally uses the Web Kit framework found inside Mac OS X to render web pages and execute javascript. This means that if you preserve an old version of Safari to run it on a newer version of Mac OS, it will use the newer Web Kit found in the system and you will get the same results as with the newer version. Thus, you would normally need a separate installation of Mac OS X for each version of Safari you want to test a website into.

]]></description>
<dc:subject>testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:22d8fd053b25/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zombie.labnotes.org/">
    <title>Insanely fast, headless full-stack testing using Node.js</title>
    <dc:date>2011-06-18T03:56:06+00:00</dc:date>
    <link>http://zombie.labnotes.org/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[If you're going to write an insanely fast, headless browser, how can you not call it Zombie? Zombie it is.

]]></description>
<dc:subject>javascript nodejs testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ef52e72a5185/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/andyedinborough/stress-css">
    <title>andyedinborough/stress-css - GitHub</title>
    <dc:date>2011-05-02T15:39:00+00:00</dc:date>
    <link>https://github.com/andyedinborough/stress-css</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[It indexes all the elements and their classes, and then--class by class--it removes one, and times how long it takes to scroll the page. Classes that save a considerable amount of time when removed indicate problem areas.]]></description>
<dc:subject>css testing performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:7b95c46dc4e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://httpstat.us/">
    <title>httpstat.us</title>
    <dc:date>2011-02-18T16:54:11+00:00</dc:date>
    <link>http://httpstat.us/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This is a super simple service for generating different HTTP codes.

It's useful for testing how your own scripts deal with varying responses.

Just add the status code you want to the URL, like this: httpstat.us/200]]></description>
<dc:subject>testing http</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:60bdff3cebbb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:http"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript">
    <title>Jeff Dean's Ruby Blog - Tips for writing testable, maintainable page-specific javascript</title>
    <dc:date>2010-12-18T00:23:17+00:00</dc:date>
    <link>http://pivotallabs.com/users/jdean/blog/articles/1497-tips-for-writing-testable-maintainable-page-specific-javascript</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I've worked on several large Rails apps and seen at least a dozen javascript systems. In this post I'll describe a few techniques that I've seen that consistently make javascript easier to test and maintain. To those of you who write javascript more than I do, these might be old news, but it's taken me 4 years to learn them!]]></description>
<dc:subject>javascript tdd testing bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:baf4b0079667/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tester.jonasjohn.de/">
    <title>Test everything</title>
    <dc:date>2009-06-16T01:07:21+00:00</dc:date>
    <link>http://tester.jonasjohn.de/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[100+ tools including SEO, validation, etc.]]></description>
<dc:subject>testing validation</dc:subject>
<dc:identifier>https://pinboard.in/u:jpcody/b:dcda092fa403/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:validation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://esbueno.noahstokes.com/post/104048692/3-step-process-for-troubleshooting-your-css-step-1">
    <title>Troubleshoot your CSS</title>
    <dc:date>2009-05-19T01:30:57+00:00</dc:date>
    <link>http://esbueno.noahstokes.com/post/104048692/3-step-process-for-troubleshooting-your-css-step-1</link>
    <dc:creator>jpcody</dc:creator><dc:subject>testing css</dc:subject>
<dc:identifier>https://pinboard.in/u:jpcody/b:e78543e824a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>