<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket Query</title>
    <link>http://localhost/query?status=!closed&amp;reporter=Dominik&amp;desc=1&amp;order=priority</link>
    <description>The open source data portal software</description>
    <language>en-US</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/query?status=!closed&amp;reporter=Dominik&amp;desc=1&amp;order=priority</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
        <link>http://localhost/ticket/2934</link>
        <guid isPermaLink="false">http://localhost/ticket/2934</guid>
        <title>#2934: Webtests for CKAN</title>
        <pubDate>Tue, 18 Sep 2012 11:10:47 GMT</pubDate>
        
        <dc:creator>Dominik</dc:creator>

        <description>&lt;p&gt;
The tests in CKAN only test single pages (functional tests) or single methods (unit tests). In order to make sure that the whole system still works as expected, we need tests that cover whole processes.
&lt;/p&gt;
&lt;p&gt;
An example user story to be tested would be:
"As a user with create permissions I want to be able to log in, create a new resource, save it and then make sure that it is in the system."
or:
"As a user I want to use the search functionality and open a resource from the search page."
&lt;/p&gt;
&lt;p&gt;
These user stories require a different testing system with interaction and processes.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/2934#changelog</comments>
    </item>
 </channel>
</rss>