<?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 (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://codeberg.org/phochste/notation3tests"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/tdd-html-templates.html"/>
	<rdf:li rdf:resource="https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/"/>
	<rdf:li rdf:resource="https://til.simonwillison.net/pytest/playwright-pytest"/>
	<rdf:li rdf:resource="https://hurl.dev/"/>
	<rdf:li rdf:resource="https://www.lambdatest.com/"/>
	<rdf:li rdf:resource="https://medium.com/javascript-in-plain-english/i-tested-a-react-app-with-jest-testing-library-and-cypress-here-are-the-differences-3192eae03850"/>
	<rdf:li rdf:resource="https://www.cypress.io/"/>
	<rdf:li rdf:resource="https://github.com/dubzzz/fuzz-rest-api"/>
	<rdf:li rdf:resource="https://github.com/dubzzz/fast-check/blob/master/documentation/1-Guides/Tips.md#model-based-testing-or-ui-test"/>
	<rdf:li rdf:resource="https://github.com/leebyron/testcheck-js/tree/master/integrations/tape-check"/>
	<rdf:li rdf:resource="https://github.com/minimaxir/big-list-of-naughty-strings"/>
	<rdf:li rdf:resource="http://lcamtuf.coredump.cx/afl/"/>
	<rdf:li rdf:resource="https://www.runscope.com/docs/radar"/>
	<rdf:li rdf:resource="http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/"/>
	<rdf:li rdf:resource="http://www.w3.org/Submission/2014/SUBM-shapes-20140211/"/>
	<rdf:li rdf:resource="https://github.com/AKSW/RDFUnit"/>
	<rdf:li rdf:resource="https://github.com/marick/Midje"/>
	<rdf:li rdf:resource="https://gist.github.com/FND/5636996"/>
	<rdf:li rdf:resource="https://github.com/cucumber/cucumber/wiki/Gherkin"/>
	<rdf:li rdf:resource="https://github.com/michaelklishin/cucumber.el"/>
	<rdf:li rdf:resource="http://ericholscher.com/blog/2009/jun/29/enable-setuppy-test-your-django-apps/"/>
	<rdf:li rdf:resource="https://developers.google.com/v8/profiler_example"/>
	<rdf:li rdf:resource="https://github.com/feuerbach/smallcheck"/>
	<rdf:li rdf:resource="https://github.com/ianb/walkabout.js"/>
	<rdf:li rdf:resource="http://doctestjs.org/"/>
	<rdf:li rdf:resource="http://www.robohornet.org/"/>
	<rdf:li rdf:resource="https://github.com/robohornet/robohornet"/>
	<rdf:li rdf:resource="http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html"/>
	<rdf:li rdf:resource="http://fakeapp.com/"/>
	<rdf:li rdf:resource="http://travis-ci.org/"/>
	<rdf:li rdf:resource="file://localhost/Users/ryanshaw/Code/qc.js/doc/userdocs/2.html"/>
	<rdf:li rdf:resource="https://bitbucket.org/darrint/qc.js/"/>
	<rdf:li rdf:resource="http://blog.whatwg.org/usability-testing-html5"/>
	<rdf:li rdf:resource="http://www.phantomjs.org/"/>
	<rdf:li rdf:resource="http://visionmedia.github.com/mocha/"/>
	<rdf:li rdf:resource="https://github.com/mhevery/jasmine-node"/>
	<rdf:li rdf:resource="http://linux.die.net/man/1/git-bisect"/>
	<rdf:li rdf:resource="http://saucelabs.com/"/>
	<rdf:li rdf:resource="https://github.com/flatiron/api-easy"/>
	<rdf:li rdf:resource="http://code.google.com/p/script-cover/"/>
	<rdf:li rdf:resource="http://csslint.net/about.html"/>
	<rdf:li rdf:resource="http://blog.nodejitsu.com/http-server"/>
	<rdf:li rdf:resource="http://watir.com/"/>
	<rdf:li rdf:resource="http://services.odata.org/validation/"/>
	<rdf:li rdf:resource="http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs"/>
	<rdf:li rdf:resource="https://github.com/maccman/ichabod"/>
	<rdf:li rdf:resource="http://vowsjs.org/"/>
	<rdf:li rdf:resource="http://blog.ianbicking.org/2010/04/02/webtest-http-testing/"/>
	<rdf:li rdf:resource="http://groups.google.com/group/python-tornado/browse_thread/thread/867cfb2665ea10a9/b106b451fa5709e0"/>
	<rdf:li rdf:resource="http://github.com/rlisagor/freshen"/>
	<rdf:li rdf:resource="http://devel.almad.net/trac/django-sane-testing/"/>
	<rdf:li rdf:resource="http://bitbucket.org/akoha/django-lean/wiki/Home"/>
	<rdf:li rdf:resource="http://somethingaboutorange.com/mrl/projects/nose/0.11.0/"/>
	<rdf:li rdf:resource="http://www.furia.com/page.cgi?type=log&amp;id=326"/>
	<rdf:li rdf:resource="http://yuiblog.com/blog/2008/12/01/yuitest-getting-started/"/>
	<rdf:li rdf:resource="http://codespeak.net/py/dist/"/>
	<rdf:li rdf:resource="http://livedom.validator.nu/"/>
	<rdf:li rdf:resource="http://www.djangoproject.com/documentation/testing/#the-test-client"/>
	<rdf:li rdf:resource="http://code.google.com/p/nose-trestle/"/>
	<rdf:li rdf:resource="http://browsershots.org/"/>
	<rdf:li rdf:resource="http://www.openqa.org/"/>
	<rdf:li rdf:resource="http://www.joehewitt.com/software/firebug/"/>
	<rdf:li rdf:resource="http://httpd.apache.org/test/flood/"/>
	<rdf:li rdf:resource="http://asunit.sourceforge.net/"/>
	<rdf:li rdf:resource="http://www.techsmith.com/products/morae/default.asp"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://codeberg.org/phochste/notation3tests">
    <title>phochste/notation3tests: A cross reasoner compliance test suite for the Notation3 language. - Codeberg.org</title>
    <dc:date>2026-03-22T20:56:03+00:00</dc:date>
    <link>https://codeberg.org/phochste/notation3tests</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A cross reasoner compliance test suite for the Notation3 language.
]]></description>
<dc:subject>n3 testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:695ad158f4c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:n3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/tdd-html-templates.html">
    <title>Test-Driving HTML Templates</title>
    <dc:date>2024-06-21T21:08:34+00:00</dc:date>
    <link>https://martinfowler.com/articles/tdd-html-templates.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[When building a server-side rendered web application, it is valuable to test the HTML that's generated through templates. While these can be tested through end-to-end tests running in the browser, such tests are slow and more work to maintain than unit tests. Unit tests, written in the server-side environment, can check for valid HTML, and extract elements with CSS selectors to test the details of generated HTML. These test cases can be defined in a simple data structure to make them easier to understand and enhance. Browser testing tools are still needed to unit test the behavior of the generated HTML, together with the associated CSS and JavaScript.]]></description>
<dc:subject>testing html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f3674884b970/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/">
    <title>Mac VoiceOver Testing the Simple Way – Cloud Four</title>
    <dc:date>2022-08-26T21:02:51+00:00</dc:date>
    <link>https://cloudfour.com/thinks/mac-voiceover-testing-the-simple-way/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An easy-to-follow, repeatable guide to make testing with VoiceOver on a Mac as simple as possible.]]></description>
<dc:subject>accessibility testing howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b543b6224a17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://til.simonwillison.net/pytest/playwright-pytest">
    <title>Using pytest and Playwright to test a JavaScript web application | Simon Willison’s TILs</title>
    <dc:date>2022-08-10T21:55:25+00:00</dc:date>
    <link>https://til.simonwillison.net/pytest/playwright-pytest</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[playwright-pytest, which lets you write tests in Python using Microsoft's Playwright browser automation library.]]></description>
<dc:subject>python web ui testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c04de05142f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hurl.dev/">
    <title>Hurl - Run and Test HTTP Requests</title>
    <dc:date>2021-11-22T14:05:17+00:00</dc:date>
    <link>https://hurl.dev/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hurl is a command line tool that runs HTTP requests defined in a simple plain text format.

It can perform requests, capture values and evaluate queries on headers and body response. Hurl is very versatile: it can be used for both fetching data and testing HTTP sessions.]]></description>
<dc:subject>http testing tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8433dd5f3ca9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.lambdatest.com/">
    <title>Most Powerful Cross Browser Testing Tool Online | LambdaTest</title>
    <dc:date>2020-12-12T23:41:06+00:00</dc:date>
    <link>https://www.lambdatest.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Perform Live Interactive and Automated Cross Browser Testing on 
2000+ Real Browsers and Operating Systems Online]]></description>
<dc:subject>testing tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b02edee8743f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/javascript-in-plain-english/i-tested-a-react-app-with-jest-testing-library-and-cypress-here-are-the-differences-3192eae03850">
    <title>I tested a React app with Jest, Enzyme, Testing Library and Cypress. Here are the differences.</title>
    <dc:date>2019-11-01T16:59:57+00:00</dc:date>
    <link>https://medium.com/javascript-in-plain-english/i-tested-a-react-app-with-jest-testing-library-and-cypress-here-are-the-differences-3192eae03850</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Finally, a side-by-side code comparison between three of the most popular testing tools for React. Watch as we attempt to write the exact same tests with Jest, Testing Library, and Cypress.]]></description>
<dc:subject>javascript react testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9cc530e06dfc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:react"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cypress.io/">
    <title>JavaScript End to End Testing Framework | cypress.io</title>
    <dc:date>2019-09-27T01:23:45+00:00</dc:date>
    <link>https://www.cypress.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Fast, easy and reliable testing for anything that runs in a browser.]]></description>
<dc:subject>javascript testing automation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e0ba9a513fe6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:automation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/dubzzz/fuzz-rest-api">
    <title>dubzzz/fuzz-rest-api: Derive property based testing fact-check into a fuzzer for REST APIs</title>
    <dc:date>2019-09-09T16:49:59+00:00</dc:date>
    <link>https://github.com/dubzzz/fuzz-rest-api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This Proof-Of-Concept uses the power of property based testing to generate inputs for a REST end-point. It sends the generated values to this end-point and check for the property - whatever the data I send I should not receive an Internal Error aka 500.]]></description>
<dc:subject>testing apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2580ed774dc5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/dubzzz/fast-check/blob/master/documentation/1-Guides/Tips.md#model-based-testing-or-ui-test">
    <title>fast-check/Tips.md at master · dubzzz/fast-check</title>
    <dc:date>2019-09-09T16:49:36+00:00</dc:date>
    <link>https://github.com/dubzzz/fast-check/blob/master/documentation/1-Guides/Tips.md#model-based-testing-or-ui-test</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Model based testing approach have been introduced into fast-check to ease UI testing or state machine tests.

The idea of the approach is to define commands that could be applied to your system. The framework then picks zero, one or more commands and run them sequentially if they can be executed on the current state.]]></description>
<dc:subject>testing apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7bcbf53df2bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/leebyron/testcheck-js/tree/master/integrations/tape-check">
    <title>testcheck-js/integrations/tape-check at master · leebyron/testcheck-js</title>
    <dc:date>2017-04-26T21:48:22+00:00</dc:date>
    <link>https://github.com/leebyron/testcheck-js/tree/master/integrations/tape-check</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[tape-check adds the generative testing power of testcheck-js to Tape. This allows some of your Tape tests to accept arguments and ensure your tests pass not just under your contrived test cases but also pass for hundreds of randomly generated test cases.]]></description>
<dc:subject>testing tools javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:09718fa19387/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/minimaxir/big-list-of-naughty-strings">
    <title>minimaxir/big-list-of-naughty-strings: The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.</title>
    <dc:date>2017-02-16T14:36:13+00:00</dc:date>
    <link>https://github.com/minimaxir/big-list-of-naughty-strings</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.]]></description>
<dc:subject>syntax testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c78cf5f962ee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:syntax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lcamtuf.coredump.cx/afl/">
    <title>american fuzzy lop</title>
    <dc:date>2015-02-24T17:16:25+00:00</dc:date>
    <link>http://lcamtuf.coredump.cx/afl/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[American fuzzy lop is a security-oriented fuzzer that employs a novel type of compile-time instrumentation and genetic algorithms to automatically discover clean, interesting test cases that trigger new internal states in the targeted binary. This substantially improves the functional coverage for the fuzzed code. The compact synthesized corpora produced by the tool are also useful for seeding other, more labor- or resource-intensive testing regimes down the road.]]></description>
<dc:subject>security testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7e7ae9837568/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.runscope.com/docs/radar">
    <title>Getting Started with API Monitoring and Testing · Runscope API Tools Documentation · Runscope</title>
    <dc:date>2014-09-30T17:31:28+00:00</dc:date>
    <link>https://www.runscope.com/docs/radar</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A Runscope Radar test is a group of one or more HTTP requests executed sequentially. For each request in the sequence you can define  Assertions on expected response data and  Variables containing extracted response data to be used in subsequent requests.]]></description>
<dc:subject>api testing inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8acb79ebc61a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/">
    <title>Shape Expressions 1.0 Primer</title>
    <dc:date>2014-09-12T12:57:38+00:00</dc:date>
    <link>http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Shape Expressions can be used to validate documents, communicate expected graph patterns for interfaces, and generate user interface forms and interface code. The syntax and semantics of Shape Expressions are designed to be familiar to users of regular expressions. The conspicuous differences are that regular expressions correlate an ordered pattern of atomic characters and logical operators against an ordered sequence of characters. Shape Expressions correlate an ordered pattern of pairs of predicate and object classes (called NameClass and ValueClass) and logical operators against an unordered set of arcs in a graph. The logical operators in Shape Expressions, grouping, conjunction, disjunction and cardinality constraints, are defined to behave as closely as possible to their counterparts in regular expressions and grammar languages like BNF.]]></description>
<dc:subject>linkeddata semweb validation cleaning testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c8542a9d339a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cleaning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/Submission/2014/SUBM-shapes-20140211/">
    <title>Resource Shape 2.0</title>
    <dc:date>2014-09-12T12:38:17+00:00</dc:date>
    <link>http://www.w3.org/Submission/2014/SUBM-shapes-20140211/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes the Resource Shape specification, a high-level RDF vocabulary for describing the shape of RDF resources. Here the term RDF resource is used to denote a resource that has an RDF document among its set of available representations. The term shape is used because it is often useful to visualize an RDF document as a topological object, namely as a graph consisting of nodes interconnected by arcs. Throughout this document the terms RDF resource, RDF document, and RDF graph are used more or less interchangeably albeit somewhat imprecisely.

The shape of an RDF graph includes both a description of its expected contents (properties, types) within some operational context (e.g. GET, POST) and the integrity constraints that must be satisfied by the contents in that context.]]></description>
<dc:subject>linkeddata semweb validation testing cleaning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:269de295060f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cleaning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/AKSW/RDFUnit">
    <title>AKSW/RDFUnit</title>
    <dc:date>2014-07-16T02:02:01+00:00</dc:date>
    <link>https://github.com/AKSW/RDFUnit</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This repository contains the RDFUnit -- a tool for test-driven quality evaluation of Linked Data quality. Further background information about the underlying Test Driven Data Quality Methodology can be looked up in the following publications: methodology (WWW2014), demo paper (WWW2014) and ontology definition (ESWC2014). The results of the methodology paper are available here . This methodology defines a set of data quality test patterns which are SPARQL query templates expressing certain common error conditions. After having instantiated such patterns for a concrete dataset possible errors of the corresponding kind can be detected.]]></description>
<dc:subject>rdf testing periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0310ee747e52/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/marick/Midje">
    <title>marick/Midje</title>
    <dc:date>2014-04-24T03:17:36+00:00</dc:date>
    <link>https://github.com/marick/Midje</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Midje is a test framework for Clojure. I created it to allow programmers to test with ease, to provide a smooth migration path from clojure.test, to support top-down as well as bottom-up testing, to encourage readable tests, to support a balance between abstraction and concreteness, and to be gracious in its treatment of the people who use it.]]></description>
<dc:subject>clojure testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c828c44100fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:clojure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gist.github.com/FND/5636996">
    <title>wsgi-intercept vs. Requests / urllib3</title>
    <dc:date>2013-05-28T16:18:48+00:00</dc:date>
    <link>https://gist.github.com/FND/5636996</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[wsgi-intercept vs. Requests / urllib3]]></description>
<dc:subject>python http testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:43f562b4a0a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cucumber/cucumber/wiki/Gherkin">
    <title>Gherkin · cucumber/cucumber Wiki</title>
    <dc:date>2013-05-28T12:41:16+00:00</dc:date>
    <link>https://github.com/cucumber/cucumber/wiki/Gherkin</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Gherkin is the language that Cucumber understands. It is a Business Readable, Domain Specific Language that lets you describe software’s behaviour without detailing how that behaviour is implemented.

Gherkin serves two purposes – documentation and automated tests. The third is a bonus feature – when it yells in red it’s talking to you, telling you what code you should write.

Gherkin’s grammar is defined in the Treetop grammar that is part of the Cucumber codebase. The grammar exists in different flavours for many spoken languages (37 at the time of writing), so that your team can use the keywords in your own language.

There are a few conventions.

Single Gherkin source file contains a description of a single feature.
Source files have .feature extension.]]></description>
<dc:subject>gherkin testing description language</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:956baf4b463f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gherkin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/michaelklishin/cucumber.el">
    <title>michaelklishin/cucumber.el · GitHub</title>
    <dc:date>2013-05-28T12:40:31+00:00</dc:date>
    <link>https://github.com/michaelklishin/cucumber.el</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Emacs mode for editing Cucumber/Gherkin plain text stories.]]></description>
<dc:subject>emacs testing gherkin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:69bbce49eeb3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gherkin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ericholscher.com/blog/2009/jun/29/enable-setuppy-test-your-django-apps/">
    <title>Enable setup.py test in your Django apps — Surfing in Kansas 1.0 documentation</title>
    <dc:date>2013-05-08T17:29:39+00:00</dc:date>
    <link>http://ericholscher.com/blog/2009/jun/29/enable-setuppy-test-your-django-apps/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Setuptools comes with a way to run the tests on your application. This allows the user of your software to download it, and run python setup.py test and check to see if the tests in your application pass. This is really useful for distribution, because the user doesn’t need to know or care how to run your tests (nose, django, unittest, py.test, or whatever else), and can simply see if they pass.]]></description>
<dc:subject>django packaging testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0792d6177cb9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:packaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/v8/profiler_example">
    <title>Profile your web application with V8’s internal profiler - Chrome V8 — Google Developers</title>
    <dc:date>2013-03-06T13:26:23+00:00</dc:date>
    <link>https://developers.google.com/v8/profiler_example</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Today's highly optimized virtual machines can run web apps at blazing speed. But one shouldn't rely only on them to achieve great performances: a carefully optimized algorithm or a less expensive function can often reach many-fold speed improvements on all browsers. Chrome Developer Tool’s CPU Profiler helps you analyzing your code bottlenecks. But sometimes, you need to go deeper and more granular: this is where V8's internal profiler comes in handy.]]></description>
<dc:subject>javascript performance testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d848ac34f16e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/feuerbach/smallcheck">
    <title>feuerbach/smallcheck · GitHub</title>
    <dc:date>2013-02-20T15:49:40+00:00</dc:date>
    <link>https://github.com/feuerbach/smallcheck</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[SmallCheck is a testing library that allows to verify properties for all test cases up to some depth. The test cases are generated automatically by SmallCheck.]]></description>
<dc:subject>haskell testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a87db5190669/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:haskell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ianb/walkabout.js">
    <title>ianb/walkabout.js</title>
    <dc:date>2012-11-30T03:26:25+00:00</dc:date>
    <link>https://github.com/ianb/walkabout.js</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This code figures out what your application is paying attention to, and does it. It fills in fields with random values. It finds the events you listen for and fires those events. It finds internal links (like <a href="#foo">) and clicks them. It's a little like a fuzz tester for your app.
]]></description>
<dc:subject>testing javascript jquery</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4862fe8dae53/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jquery"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://doctestjs.org/">
    <title>Doctest.js: the humane Javascript test framework</title>
    <dc:date>2012-10-03T03:59:39+00:00</dc:date>
    <link>http://doctestjs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Doctest.js is a test runner and testing framework for Javascript.

Doctest uses a novel approach to testing: example and expected result. Each test is a chunk of code that prints out results and side effects, and then the expected result is matched against that to see if the test passed or failed.]]></description>
<dc:subject>javascript testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:185d9008248a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.robohornet.org/">
    <title>RoboHornet</title>
    <dc:date>2012-09-24T23:55:54+00:00</dc:date>
    <link>http://www.robohornet.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RoboHornet is a benchmark designed around peformance pain points real web developers care about. ]]></description>
<dc:subject>testing QA performance web measurement design collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3df0b37aeba0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:QA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/robohornet/robohornet">
    <title>robohornet/robohornet</title>
    <dc:date>2012-09-24T23:55:11+00:00</dc:date>
    <link>https://github.com/robohornet/robohornet</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Every benchmark in the suite is designed to capture a performance pain point in a measurable way, such that an improvement in the benchmark's speed represents a lessening of felt pain. Any performance pain point is fair game—not just the ones that involve JavaScript. The suite uses a novel scoring system to represent the overall score as intuitively as possible. The community proposes performance painpoints to highlight and votes on which ones affect them most. A small group of stewards then distills the community's desires into regular, curated updates to the benchmark suite, allowing it to grow and evolve over time.]]></description>
<dc:subject>performance testing collaboration design measurement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f16d8411e441/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html">
    <title>RoboHornet: The Next Big Thing In Browser Benchmarking : RoboHornet: The Top Five Browsers, Tested And Ranked</title>
    <dc:date>2012-09-24T23:53:08+00:00</dc:date>
    <link>http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RoboHornet is a framework for a scalable, evolving performance metric. The “benchmark” is actually a modular suite of performance tests. These tests are created and voted on by a community of Web designers and developers, with standards boards and other Web heavyweights acting as stewards. We can confirm that Google, Facebook, Microsoft, and Mozilla are currently listed as stewards. The browser vendors and other Web companies can also get involved as technical advisers to the project. Even regular users can contribute to RoboHornet by raising issues, voting up existing issues, or even writing benchmarks.]]></description>
<dc:subject>design testing performance metrics web collaboration measurement inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5c23b9d14584/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fakeapp.com/">
    <title>Fake - Mac OS X Web Browser Automation and Webapp Testing Made Simple.</title>
    <dc:date>2012-05-25T12:18:44+00:00</dc:date>
    <link>http://fakeapp.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Fake is a new browser for Mac OS X that makes web automation simple. Fake allows you to drag discrete browser Actions into a graphical Workflow that can be run again and again without human interaction. The Fake Workflows you create can be saved, reopened, and shared.]]></description>
<dc:subject>mac osx web automation testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:287bd0d32f0c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://travis-ci.org/">
    <title>Travis CI - Distributed build platform for the open source community</title>
    <dc:date>2012-04-10T01:36:37+00:00</dc:date>
    <link>http://travis-ci.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[hosting your project on travis-ci.org means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.]]></description>
<dc:subject>nodejs testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d6d2947dae40/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="file://localhost/Users/ryanshaw/Code/qc.js/doc/userdocs/2.html">
    <title>JsDoc Reference - File Index</title>
    <dc:date>2012-04-07T02:52:17+00:00</dc:date>
    <link>file://localhost/Users/ryanshaw/Code/qc.js/doc/userdocs/2.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The core ethic of what we are doing with qc.js is coming up with "properties" our code should have and verifying that those properties actually hold in practice.]]></description>
<dc:subject>javascript testing functional coffeescript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b287bf60fea2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:coffeescript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://bitbucket.org/darrint/qc.js/">
    <title>darrint / qc.js / overview — Bitbucket</title>
    <dc:date>2012-04-06T20:54:33+00:00</dc:date>
    <link>https://bitbucket.org/darrint/qc.js/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a port of the QuickCheck probabilistic unit testing concept to JavaScript.]]></description>
<dc:subject>javascript testing framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:06638cebdd44/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.whatwg.org/usability-testing-html5">
    <title>The WHATWG Blog — Usability testing HTML5</title>
    <dc:date>2012-03-29T13:25:04+00:00</dc:date>
    <link>http://blog.whatwg.org/usability-testing-html5</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Google's usability study to test the microdata feature of HTML5.]]></description>
<dc:subject>microdata usability testing inls620 html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c24d312d334e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:microdata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.phantomjs.org/">
    <title>PhantomJS: Headless WebKit with JavaScript API</title>
    <dc:date>2012-02-02T18:59:42+00:00</dc:date>
    <link>http://www.phantomjs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[PhantomJS is a headless WebKit with JavaScript API. It has fast and native support for various web standards: DOM handling, CSS selector, JSON, Canvas, and SVG.

PhantomJS is an optimal solution for fast headless testing, site scraping, pages capture, SVG renderer, network monitoring and many other use cases.]]></description>
<dc:subject>javascript scraping testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f684eaa5375e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scraping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://visionmedia.github.com/mocha/">
    <title>Mocha - the fun, simple, flexible JavaScript test framework</title>
    <dc:date>2012-01-25T15:13:17+00:00</dc:date>
    <link>http://visionmedia.github.com/mocha/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Mocha is a feature-rich JavaScript test framework running on node and the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases.]]></description>
<dc:subject>nodejs javascript testing qa</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ed1fbcd9ab38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:qa"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mhevery/jasmine-node">
    <title>mhevery/jasmine-node - GitHub</title>
    <dc:date>2012-01-24T19:54:57+00:00</dc:date>
    <link>https://github.com/mhevery/jasmine-node</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Write the specifications for your code in *.js and *.coffee files in the spec/ directory (note: your specification files must end with either .spec.js or .spec.coffee; otherwise jasmine-node won't find them!). You can use sub-directories to better organise your specs.]]></description>
<dc:subject>javascript nodejs testing qa coffeescript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9a988eeab999/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:qa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:coffeescript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://linux.die.net/man/1/git-bisect">
    <title>git-bisect(1) - Linux man page</title>
    <dc:date>2011-11-24T13:21:31+00:00</dc:date>
    <link>http://linux.die.net/man/1/git-bisect</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This command uses git rev-list --bisect to help drive the binary search process to find which change introduced a bug, given an old "good" commit object name and a later "bad" commit object name.]]></description>
<dc:subject>debugging development qa testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:62e7529b34aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:debugging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:qa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://saucelabs.com/">
    <title>Cross browser testing with Selenium - Sauce Labs</title>
    <dc:date>2011-11-16T18:51:12+00:00</dc:date>
    <link>http://saucelabs.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Pain Free Cross~Browser Debugging & Testing.]]></description>
<dc:subject>automation cloud testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:21ed4020c1c3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/flatiron/api-easy">
    <title>flatiron/api-easy - GitHub</title>
    <dc:date>2011-11-09T21:04:03+00:00</dc:date>
    <link>https://github.com/flatiron/api-easy</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[APIeasy is designed to be a simple way to test RESTful APIs in node.js and Javascript. The primary design goal was to reduce the number of lines of test code required to fully cover all primary and edge use cases of a given API over HTTP.]]></description>
<dc:subject>rest api testing nodejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5761a6293ff4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/script-cover/">
    <title>script-cover - Javascript code coverage detector for web pages in Chrome - Google Project Hosting</title>
    <dc:date>2011-10-27T16:20:49+00:00</dc:date>
    <link>http://code.google.com/p/script-cover/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[SCRIPTCOVER is a Chrome extension for Javascript coverage analysis.

It reports which Javascript statements/instructions from internal and external scripts have been executed (and how many times) while a web page loads and then when a user interacts with the page without any user modifications to the code.]]></description>
<dc:subject>javascript performance tools testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0e2f11f94ea9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://csslint.net/about.html">
    <title>About</title>
    <dc:date>2011-06-17T12:28:08+00:00</dc:date>
    <link>http://csslint.net/about.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CSS Lint is a tool to help point out problems with your CSS code. It does basic syntax checking as well as applying a set of rules to the code that look for problematic patterns or signs of inefficiency. The rules are all pluggable, so you can easily write your own or omit ones you don't want.]]></description>
<dc:subject>css testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cc7bd2cf6b93/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.nodejitsu.com/http-server">
    <title>http-server, a command-line http server - blog.nodejitsu.com - scaling node.js applications one callback at a time.</title>
    <dc:date>2011-06-17T12:10:06+00:00</dc:date>
    <link>http://blog.nodejitsu.com/http-server</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[http-server is a simple, zero-configuration command-line http server. It is powerful enough for production usage, but it's simple and hackable enough to be used for testing, local development, and learning.]]></description>
<dc:subject>node http testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9de0dd14c86c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:node"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://watir.com/">
    <title>Watir</title>
    <dc:date>2011-04-28T12:57:38+00:00</dc:date>
    <link>http://watir.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Watir, pronounced water, is an open-source (BSD) family of Ruby libraries for automating web browsers. It allows you to write tests that are easy to read and maintain. It is simple and flexible.]]></description>
<dc:subject>automation ruby web development testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:54629228f3bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://services.odata.org/validation/">
    <title>OData Validator</title>
    <dc:date>2011-04-15T16:54:00+00:00</dc:date>
    <link>http://services.odata.org/validation/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The goal of this tool is to enable OData service authors to validate their implementation against the OData specification to ensure the service interoperates well with any OData client.
]]></description>
<dc:subject>odata tools validation testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7a3c95e4e731/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:odata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs">
    <title>RESTeasy: Test any API in node.js - blog.nodejitsu.com - scaling node.js applications one callback at a time.</title>
    <dc:date>2011-04-14T03:54:10+00:00</dc:date>
    <link>http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A simple tool for writing behavior-driven tests for any REST API.]]></description>
<dc:subject>rest api testing nodejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d98ec8f968fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/maccman/ichabod">
    <title>maccman/ichabod - GitHub</title>
    <dc:date>2011-03-22T14:05:52+00:00</dc:date>
    <link>https://github.com/maccman/ichabod</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Run JavaScript tests from the command line using a headless version of WebKit.]]></description>
<dc:subject>mac javascript testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e797af64b91e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vowsjs.org/">
    <title>Vows « Asynchronous BDD for Node</title>
    <dc:date>2011-02-20T18:37:46+00:00</dc:date>
    <link>http://vowsjs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Asynchronous behaviour driven development for Node.]]></description>
<dc:subject>nodejs testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:01c19128df4d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.ianbicking.org/2010/04/02/webtest-http-testing/">
    <title>Ian Bicking: a blog :: WebTest HTTP testing</title>
    <dc:date>2010-04-02T23:17:15+00:00</dc:date>
    <link>http://blog.ianbicking.org/2010/04/02/webtest-http-testing/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[If you are running local tests against your application using WebTest, with just a little tweaking you can turn those tests into HTTP tests (i.e., actually connect to a socket).]]></description>
<dc:subject>python testing web</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e6eb10fce905/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.google.com/group/python-tornado/browse_thread/thread/867cfb2665ea10a9/b106b451fa5709e0">
    <title>Unit testing a Tornado web application - Tornado Web Server | Google Groups</title>
    <dc:date>2010-01-22T21:44:15+00:00</dc:date>
    <link>http://groups.google.com/group/python-tornado/browse_thread/thread/867cfb2665ea10a9/b106b451fa5709e0</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A fully-functional Python unittest example where we have a Tornado web application that is being tested.
]]></description>
<dc:subject>python tornado testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:12176fb738f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tornado"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/rlisagor/freshen">
    <title>rlisagor's freshen at master - GitHub</title>
    <dc:date>2010-01-05T21:07:54+00:00</dc:date>
    <link>http://github.com/rlisagor/freshen</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Freshen is an acceptance testing framework for Python.
]]></description>
<dc:subject>python django testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:50365f73d9af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://devel.almad.net/trac/django-sane-testing/">
    <title>Django: sane testing</title>
    <dc:date>2010-01-05T21:02:40+00:00</dc:date>
    <link>http://devel.almad.net/trac/django-sane-testing/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This library contains various fixes and support/integration for various 3rd party tools that make developers live easier.
]]></description>
<dc:subject>django testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:55e83dbf2bdc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bitbucket.org/akoha/django-lean/wiki/Home">
    <title>django-lean</title>
    <dc:date>2009-10-06T00:15:50+00:00</dc:date>
    <link>http://bitbucket.org/akoha/django-lean/wiki/Home</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A framework for performing and analyzing split-test experiments in Django applications.
]]></description>
<dc:subject>django usability testing framework</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:5b641a7f7006/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://somethingaboutorange.com/mrl/projects/nose/0.11.0/">
    <title>Installation and quick start — nose v0.11.0 documentation</title>
    <dc:date>2009-05-08T17:07:57+00:00</dc:date>
    <link>http://somethingaboutorange.com/mrl/projects/nose/0.11.0/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[nose extends unittest to make testing easier.
]]></description>
<dc:subject>python testing tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:d5de4e84c96e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.furia.com/page.cgi?type=log&amp;id=326">
    <title>The Problem with Answers</title>
    <dc:date>2009-03-28T18:35:31+00:00</dc:date>
    <link>http://www.furia.com/page.cgi?type=log&amp;id=326</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The great disadvantage of testing and data is that you get precise, decisive answers you can and will act on, but you almost never know what question you really asked.
]]></description>
<dc:subject>data research methods interpretation science engineering design testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:30f53668eb09/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interpretation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yuiblog.com/blog/2008/12/01/yuitest-getting-started/">
    <title>Getting Started with JavaScript Unit Testing and YUI Test » Yahoo! User Interface Blog</title>
    <dc:date>2008-12-01T17:31:22+00:00</dc:date>
    <link>http://yuiblog.com/blog/2008/12/01/yuitest-getting-started/</link>
    <dc:creator>rybesh</dc:creator><dc:subject>testing javascript howto</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:f2213590d7e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codespeak.net/py/dist/">
    <title>py lib</title>
    <dc:date>2008-11-19T05:06:27+00:00</dc:date>
    <link>http://codespeak.net/py/dist/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The py lib is a development support library featuring py.test, ad-hoc distributed execution, micro-threads (greenlets) and uniform local path and svn abstractions.
]]></description>
<dc:subject>python development tools testing code</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a06f321d184d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://livedom.validator.nu/">
    <title>Live DOM Viewer</title>
    <dc:date>2008-08-14T18:24:08+00:00</dc:date>
    <link>http://livedom.validator.nu/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Live DOM Viewer with an HTML5 parser running as JavaScript in your browser.
]]></description>
<dc:subject>dom tools javascript authoring testing html</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:97542c1bd9bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.djangoproject.com/documentation/testing/#the-test-client">
    <title>Django | Testing Django applications | Django Documentation</title>
    <dc:date>2008-07-04T15:36:05+00:00</dc:date>
    <link>http://www.djangoproject.com/documentation/testing/#the-test-client</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The test client is a Python class that acts as a dummy Web browser, allowing you to test your views and interact with your Django-powered application programatically.
]]></description>
<dc:subject>python web development django testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:d0afb7b61a6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/nose-trestle/">
    <title>nose-trestle - Google Code</title>
    <dc:date>2008-03-19T15:51:52+00:00</dc:date>
    <link>http://code.google.com/p/nose-trestle/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Trestle is a nose plugin that enables you to write testable documentation for web apps.
]]></description>
<dc:subject>python rest webservices testing tools code</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:21a0afbe0e15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://browsershots.org/">
    <title>Test your web design in different browsers - Browsershots</title>
    <dc:date>2008-02-27T17:01:33+00:00</dc:date>
    <link>http://browsershots.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Browsershots makes screenshots of your web design in different browsers.
]]></description>
<dc:subject>web design testing tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:85a6dbc0e5d3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.openqa.org/">
    <title>OpenQA: Home</title>
    <dc:date>2007-04-02T01:15:06+00:00</dc:date>
    <link>http://www.openqa.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OpenQA is the premier source for quality open source QA projects.
]]></description>
<dc:subject>testing usability code development opensource tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:eaf597cf195c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.joehewitt.com/software/firebug/">
    <title>FireBug - JoeHewitt.com</title>
    <dc:date>2006-05-31T15:47:32+00:00</dc:date>
    <link>http://www.joehewitt.com/software/firebug/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[All of the tools you need to poke, prod, and monitor your JavaScript, CSS, HTML and Ajax are brought together into one seamless experience, including a debugger, error console, command line, and a variety of fun inspectors.
]]></description>
<dc:subject>css javascript tools development design xml web testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:518080785607/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://httpd.apache.org/test/flood/">
    <title>Flood</title>
    <dc:date>2006-03-27T19:56:35+00:00</dc:date>
    <link>http://httpd.apache.org/test/flood/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Flood is a profile-driven HTTP load tester.
]]></description>
<dc:subject>web performance testing tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ac75720df7c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://asunit.sourceforge.net/">
    <title>AsUnit : A Unit Test Framework for ActionScript 2.0</title>
    <dc:date>2005-10-14T17:42:42+00:00</dc:date>
    <link>http://asunit.sourceforge.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ AsUnit is an Open-Source, Unit Test Framework for Macromedia Flash ActionScript 2.0.
]]></description>
<dc:subject>flash development code tools opensource testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:4e67e673d986/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:flash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.techsmith.com/products/morae/default.asp">
    <title>Morae: A Complete Usability Testing Solution for Web Sites and Software</title>
    <dc:date>2005-07-30T20:28:38+00:00</dc:date>
    <link>http://www.techsmith.com/products/morae/default.asp</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Morae is an all-digital usability testing solution that lets you see real users – including their verbal and facial expressions – as they experience your software, Web site, or Web application.
]]></description>
<dc:subject>usability tools research testing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab9251b4c767/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>