<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>TestFirstUserInterfaces at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/</link>
    <description>TestFirstUserInterfaces</description>

    <item>
      <title>doesn&#39;t... even... have... assert... match</title>
      <pubDate>Fri, 06 Nov 2009 12:50:11 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1051</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1051</guid>
      <description>[sorry about the premature submit!] TFUI: Testing views is not always about testing thru-the-view, like capture-playback tests, or Watir or Selenium tests,</description>
    </item>
    <item>
      <title>Re: why is Presenter First better for TDD?</title>
      <pubDate>Fri, 07 Aug 2009 21:36:19 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1049</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1049</guid>
      <description>... WikiPedia might possibly be ... (mumble) ... incorrect. It has been known to happen before. It&#39;s certainly just an aberration. ... If &quot;presenter first&quot; is</description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Tue, 16 Jun 2009 19:05:46 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1048</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1048</guid>
      <description>... Here&#39;s a metaphor - the Golden Spike at Promontory Point, Utah, where the Union Pacific and Central Pacific railways met for our first intercontinental</description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Fri, 12 Jun 2009 14:25:57 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1047</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1047</guid>
      <description>... To add a new feature, you should generally add it at the business layer first. The goal will be that anything a user can do to the View, a unit test can</description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Fri, 12 Jun 2009 04:49:24 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1046</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1046</guid>
      <description>... Could anyone here who&#39;s familiar with both ASP&#39;s Response.Write, and with Rails&#39;s ActionController::TestCase&#39;s get() method, write a little pseudocode here</description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Fri, 12 Jun 2009 04:45:53 GMT</pubDate>
      <dc:creator>miguel de sousa</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1045</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1045</guid>
      <description>Re: Can ASP render a page back as a string. Absolutely! Its call Response.Write, just pipe it out to whatever channel you like :) Regards, Miguel de Sousa </description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Fri, 12 Jun 2009 03:48:21 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1044</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1044</guid>
      <description>... Unit testing the presentation layer should treat the test targets the same as any other layer would test them. In web programming, a web page is a big</description>
    </item>
    <item>
      <title>Re: [agile-testing] Unit Testing the Presentation Layer</title>
      <pubDate>Fri, 12 Jun 2009 02:24:10 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1043</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1043</guid>
      <description>... Will ASP allow you to cook a web page without sending it over the wire? If you Mock The Server, you can then test - even TDD - by writing assertions that</description>
    </item>
    <item>
      <title>Re: Test Driven Design and Rails Helpers</title>
      <pubDate>Sun, 17 May 2009 21:28:40 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1042</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1042</guid>
      <description>... Here is a bit of hemming and hawing, while I work on projects other than assert_xhtml and assert_rjs_ (as seen at http://c2.com/cgi/wiki?AssertXhtml ) TDD</description>
    </item>
    <item>
      <title>Re: [agile-testing] Re: Using examples to drive development</title>
      <pubDate>Wed, 18 Mar 2009 02:34:25 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1041</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1041</guid>
      <description>... I have to confess a low rate of adoption for my assert_xpath project, to unit-test raw HTML. As a computer scientist and a DSL-zealot, I _like_ writing </description>
    </item>
    <item>
      <title>Re: Unit testing cost</title>
      <pubDate>Thu, 12 Mar 2009 12:37:39 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1040</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1040</guid>
      <description>... Tests also help you go faster, not just detect faults. Consider this example: &lt;div style=&#39;color: red&#39;&gt; &lt;div style=&#39;background-color: green&#39;&gt; To assert that</description>
    </item>
    <item>
      <title>Re: asserting HTML by example</title>
      <pubDate>Thu, 12 Mar 2009 12:29:22 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1039</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1039</guid>
      <description>... Try writing the equivalent of my assertion with it. I suspect you can&#39;t, because it can&#39;t constrain the element order. And the rest would be extremely</description>
    </item>
    <item>
      <title>Re: asserting HTML by example</title>
      <pubDate>Thu, 12 Mar 2009 05:33:29 GMT</pubDate>
      <dc:creator>Jason Citron</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1038</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1038</guid>
      <description>For structural HTML testing you should check out assert_select. It comes with Rails 2.0. Useful for testing XML too. </description>
    </item>
    <item>
      <title>asserting HTML by example</title>
      <pubDate>Thu, 12 Mar 2009 05:28:05 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1037</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1037</guid>
      <description>extremists: HTML is easy to test and hard to test well. A unit test must intercept and parse it, hopefully _before_ it goes thru a web server. I just wrote an</description>
    </item>
    <item>
      <title>custom, nested HTML matchers in RSpec</title>
      <pubDate>Mon, 09 Mar 2009 06:59:23 GMT</pubDate>
      <dc:creator>Phlip</dc:creator>
      <link>http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1036</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/TestFirstUserInterfaces/message/1036</guid>
      <description>... Boom: http://gist.github.com/76136 it &#39;should have a form with a fieldset&#39; do render &#39;/users/new&#39; response.body.should be_html_with{ form :action =&gt;</description>
    </item>

  </channel>
</rss>
<!-- wr1.grp.sp2.yahoo.com uncompressed/chunked Sat Nov 21 13:26:04 PST 2009 -->
