Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Site updated at 2012-12-20 17:04:24 UTC

  • Loading branch information...
commit 4eb75d13bb348f2269aed158c56d5157aa6f94e3 1 parent 24c2729
@luisalima authored
Showing with 560 additions and 106 deletions.
  1. +29 −1 atom.xml
  2. +174 −0 blog/2012/12/20/how-i-test-part-iii/index.html
  3. +19 −1 blog/archives/index.html
  4. +1 −1  blog/categories/analytics/atom.xml
  5. +1 −1  blog/categories/blog/atom.xml
  6. +1 −1  blog/categories/business/atom.xml
  7. +1 −1  blog/categories/console/atom.xml
  8. +1 −1  blog/categories/cool-gems/atom.xml
  9. +1 −1  blog/categories/future/atom.xml
  10. +1 −1  blog/categories/grooveshark/atom.xml
  11. +1 −1  blog/categories/inspiring/atom.xml
  12. +1 −1  blog/categories/interesting/atom.xml
  13. +1 −1  blog/categories/js/atom.xml
  14. +1 −1  blog/categories/log/atom.xml
  15. +1 −1  blog/categories/message/atom.xml
  16. +1 −1  blog/categories/octopress/atom.xml
  17. +1 −1  blog/categories/ot/atom.xml
  18. +1 −1  blog/categories/rails-tips/atom.xml
  19. +29 −14 blog/categories/rails/atom.xml
  20. +18 −0 blog/categories/rails/index.html
  21. +1 −1  blog/categories/raspberrypi/atom.xml
  22. +29 −1 blog/categories/rspec/atom.xml
  23. +18 −0 blog/categories/rspec/index.html
  24. +1 −1  blog/categories/ssh/atom.xml
  25. +1 −1  blog/categories/talks/atom.xml
  26. +29 −1 blog/categories/tdd/atom.xml
  27. +18 −0 blog/categories/tdd/index.html
  28. +1 −1  blog/categories/ted/atom.xml
  29. +29 −1 blog/categories/testing/atom.xml
  30. +18 −0 blog/categories/testing/index.html
  31. +1 −1  blog/categories/thin/atom.xml
  32. +1 −1  blog/categories/verbose/atom.xml
  33. +1 −1  blog/categories/vnc/atom.xml
  34. +1 −1  blog/categories/webdev/atom.xml
  35. +1 −1  blog/categories/webrick/atom.xml
  36. +60 −1 blog/page/2/index.html
  37. +60 −60 index.html
  38. +6 −2 sitemap.xml
View
30 atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
@@ -14,6 +14,34 @@
<entry>
+ <title type="html"><![CDATA[How I test part III: Why rspec?]]></title>
+ <link href="http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/"/>
+ <updated>2012-12-20T16:48:00+00:00</updated>
+ <id>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii</id>
+ <content type="html"><![CDATA[<p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing &#8211; ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don&#8217;t know exactly what you&#8217;re testing (I confess that I like Test::Unit more because it&#8217;s simpler for developers to read &#8211; assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation &#8211; the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO &#8211; yup, that&#8217;s right. If you have features that you want to implement later on, just add a &#8220;pending&#8221; spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it&#8217;s not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I&#8217;m really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here&#8217;s an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I&#8217;m abiding by this rule from the last post:</p>
+
+<p>&#8221;- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long.&#8221;</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought&#8230; why bother, exactly? It&#8217;s better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+]]></content>
+ </entry>
+
+ <entry>
<title type="html"><![CDATA[How I test part II - testing models]]></title>
<link href="http://luisalima.github.com/blog/2012/12/19/how-i-test-part-ii/"/>
<updated>2012-12-19T10:17:00+00:00</updated>
View
174 blog/2012/12/20/how-i-test-part-iii/index.html
@@ -0,0 +1,174 @@
+
+<!DOCTYPE HTML>
+<html>
+<head>
+ <meta charset="utf-8">
+ <title>How I test part III: Why rspec? - Entreprevelopment adventures</title>
+ <meta name="author" content="Luisa Lima">
+
+
+ <meta name="description" content="Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all &hellip;">
+
+ <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
+
+ <link href="/atom.xml" rel="alternate" title="Entreprevelopment adventures" type="application/atom+xml">
+ <link rel="canonical" href="">
+ <link href="/favicon.png" rel="shortcut icon">
+ <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
+ <!--[if lt IE 9]><script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
+ <script src="//ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script>
+
+</head>
+
+<body>
+ <header id="header" class="inner"><h1><a href="/">Entreprevelopment adventures</a></h1>
+<nav id="main-nav"><ul class="main">
+ <li><a href="/">Blog</a></li>
+ <li><a href="/blog/archives">Archives</a></li>
+</ul>
+</nav>
+<nav id="mobile-nav">
+ <div class="alignleft menu">
+ <a class="button">Menu</a>
+ <div class="container"><ul class="main">
+ <li><a href="/">Blog</a></li>
+ <li><a href="/blog/archives">Archives</a></li>
+</ul>
+</div>
+ </div>
+ <div class="alignright search">
+ <a class="button"></a>
+ <div class="container">
+ <form action="http://google.com/search" method="get">
+ <input type="text" name="q" results="0">
+ <input type="hidden" name="q" value="site:luisalima.github.com">
+ </form>
+ </div>
+ </div>
+</nav>
+<nav id="sub-nav" class="alignright">
+ <div class="social">
+
+
+
+ <a class="twitter" href="http://twitter.com/luisamoyalima" title="Twitter">Twitter</a>
+
+
+ <a class="github" href="https://github.com/luisalima" title="GitHub">GitHub</a>
+
+
+
+
+
+
+
+ <a class="rss" href="/atom.xml" title="RSS">RSS</a>
+
+ </div>
+ <form class="search" action="http://google.com/search" method="get">
+ <input class="alignright" type="text" name="q" results="0">
+ <input type="hidden" name="q" value="site:luisalima.github.com">
+ </form>
+</nav>
+
+</header>
+
+
+<div id="banner" class="inner">
+ <div class="container">
+ <ul class="feed"></ul>
+ </div>
+ <small><a href="http://twitter.com/luisamoyalima">luisamoyalima</a> @ <a href="http://twitter.com">Twitter</a></small>
+ <div class="loading">Loading...</div>
+</div>
+<script src="/javascripts/twitter.js"></script>
+<script type="text/javascript">
+ (function($){
+ $('#banner').getTwitterFeed('luisamoyalima', 4, false);
+ })(jQuery);
+</script>
+
+
+ <div id="content" class="inner"><article class="post">
+ <h2 class="title">How I Test Part III: Why Rspec?</h2>
+ <div class="entry-content"><p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing &#8211; ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don&#8217;t know exactly what you&#8217;re testing (I confess that I like Test::Unit more because it&#8217;s simpler for developers to read &#8211; assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation &#8211; the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO &#8211; yup, that&#8217;s right. If you have features that you want to implement later on, just add a &#8220;pending&#8221; spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it&#8217;s not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I&#8217;m really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here&#8217;s an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I&#8217;m abiding by this rule from the last post:</p>
+
+<p>&#8221;- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long.&#8221;</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought&#8230; why bother, exactly? It&#8217;s better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+</div>
+
+
+<div class="meta">
+ <div class="date">
+
+
+
+
+
+
+
+
+
+
+
+<time datetime="2012-12-20T16:48:00+00:00" pubdate data-updated="true">Dec 20<span>th</span>, 2012</time></div>
+ <div class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</div>
+
+</div></article>
+
+ <div class="share">
+ <div class="addthis_toolbox addthis_default_style ">
+
+
+ <a class="addthis_button_tweet"></a>
+
+
+ <a class="addthis_counter addthis_pill_style"></a>
+ </div>
+ <script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#pubid="></script>
+</div>
+
+
+</div>
+ <footer id="footer" class="inner">Copyright &copy; 2012
+
+ Luisa Lima
+
+</footer>
+ <script src="/javascripts/slash.js"></script>
+<script src="/javascripts/jquery.fancybox.pack.js"></script>
+<script type="text/javascript">
+(function($){
+ $('.fancybox').fancybox();
+})(jQuery);
+</script> <!-- Delete or comment this line to disable Fancybox -->
+
+
+
+
+
+
+</body>
+</html>
View
20 blog/archives/index.html
@@ -7,7 +7,7 @@
<meta name="author" content="Luisa Lima">
- <meta name="description" content="2012 How I test part II - testing models Dec 19 TDD, rails, rails_tips, rspec, testing Inspiring TED talk Dec 18 business, inspiring, talks, ted &hellip;">
+ <meta name="description" content="2012 How I test part III: Why rspec? Dec 20 TDD, rails, rspec, testing How I test part II - testing models Dec 19 TDD, rails, rails_tips, rspec, &hellip;">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
@@ -98,6 +98,24 @@
<section class="archives"><h1 class="year">2012</h1>
<article>
+ <h2 class="title"><a href="/blog/2012/12/20/how-i-test-part-iii/">How I test part III: Why rspec?</a></h2>
+ <div class="meta">
+ <span class="date">Dec 20</span>
+ <span class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</span>
+
+ </div>
+</article>
+
+
+
+
+<article>
<h2 class="title"><a href="/blog/2012/12/19/how-i-test-part-ii/">How I test part II - testing models</a></h2>
<div class="meta">
<span class="date">Dec 19</span>
View
2  blog/categories/analytics/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: analytics | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/analytics/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/blog/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: blog | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/blog/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/business/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: business | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/business/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/console/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: console | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/console/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/cool-gems/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: cool_gems | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/cool-gems/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/future/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: future | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/future/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/grooveshark/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: grooveshark | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/grooveshark/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/inspiring/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: inspiring | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/inspiring/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/interesting/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: interesting | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/interesting/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/js/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: js | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/js/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/log/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: log | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/log/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/message/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: message | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/message/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/octopress/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: octopress | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/octopress/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/ot/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: OT | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/ot/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/rails-tips/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: rails_tips | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/rails-tips/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
43 blog/categories/rails/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: rails | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/rails/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
@@ -14,6 +14,34 @@
<entry>
+ <title type="html"><![CDATA[How I test part III: Why rspec?]]></title>
+ <link href="http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/"/>
+ <updated>2012-12-20T16:48:00+00:00</updated>
+ <id>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii</id>
+ <content type="html"><![CDATA[<p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing -- ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don't know exactly what you're testing (I confess that I like Test::Unit more because it's simpler for developers to read -- assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation -- the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO -- yup, that's right. If you have features that you want to implement later on, just add a "pending" spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it's not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I'm really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here's an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I'm abiding by this rule from the last post:</p>
+
+<p>"- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long."</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought... why bother, exactly? It's better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+]]></content>
+ </entry>
+
+ <entry>
<title type="html"><![CDATA[How I test part II - testing models]]></title>
<link href="http://luisalima.github.com/blog/2012/12/19/how-i-test-part-ii/"/>
<updated>2012-12-19T10:17:00+00:00</updated>
@@ -253,17 +281,4 @@ end
]]></content>
</entry>
- <entry>
- <title type="html"><![CDATA[Rails tip #1 - environment variables]]></title>
- <link href="http://luisalima.github.com/blog/2012/12/14/rails-tip-number-1-environment-variables/"/>
- <updated>2012-12-14T10:24:00+00:00</updated>
- <id>http://luisalima.github.com/blog/2012/12/14/rails-tip-number-1-environment-variables</id>
- <content type="html"><![CDATA[<p>This isn't exactly my tip (well, since this is a learning / work in progress blog, none of them are), but when an article is already as comprehensive as this one, there's nothing left to say except:</p>
-
-<p><a href="http://railsapps.github.com/rails-environment-variables.html">Here's a very nice article on the options for setting environment variables in Rails</a></p>
-
-<p>Why would you want to set environment variables in rails? There are some examples in the article, but for instance, setting passwords to access services. They should not be in any file (nor tracked in git), so that other people cannot access them. One way is to set Unix environment variables, the other way -- which actually sounds like a "cleaner way" of organizing things -- is to set them from Rails itself by taking the values from a yaml file.</p>
-]]></content>
- </entry>
-
</feed>
View
18 blog/categories/rails/index.html
@@ -98,6 +98,24 @@
<section class="archives"><h1 class="year">2012</h1>
<article>
+ <h2 class="title"><a href="/blog/2012/12/20/how-i-test-part-iii/">How I test part III: Why rspec?</a></h2>
+ <div class="meta">
+ <span class="date">Dec 20</span>
+ <span class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</span>
+
+ </div>
+</article>
+
+
+
+
+<article>
<h2 class="title"><a href="/blog/2012/12/19/how-i-test-part-ii/">How I test part II - testing models</a></h2>
<div class="meta">
<span class="date">Dec 19</span>
View
2  blog/categories/raspberrypi/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: raspberrypi | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/raspberrypi/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
30 blog/categories/rspec/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: rspec | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/rspec/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
@@ -14,6 +14,34 @@
<entry>
+ <title type="html"><![CDATA[How I test part III: Why rspec?]]></title>
+ <link href="http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/"/>
+ <updated>2012-12-20T16:48:00+00:00</updated>
+ <id>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii</id>
+ <content type="html"><![CDATA[<p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing -- ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don't know exactly what you're testing (I confess that I like Test::Unit more because it's simpler for developers to read -- assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation -- the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO -- yup, that's right. If you have features that you want to implement later on, just add a "pending" spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it's not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I'm really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here's an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I'm abiding by this rule from the last post:</p>
+
+<p>"- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long."</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought... why bother, exactly? It's better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+]]></content>
+ </entry>
+
+ <entry>
<title type="html"><![CDATA[How I test part II - testing models]]></title>
<link href="http://luisalima.github.com/blog/2012/12/19/how-i-test-part-ii/"/>
<updated>2012-12-19T10:17:00+00:00</updated>
View
18 blog/categories/rspec/index.html
@@ -98,6 +98,24 @@
<section class="archives"><h1 class="year">2012</h1>
<article>
+ <h2 class="title"><a href="/blog/2012/12/20/how-i-test-part-iii/">How I test part III: Why rspec?</a></h2>
+ <div class="meta">
+ <span class="date">Dec 20</span>
+ <span class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</span>
+
+ </div>
+</article>
+
+
+
+
+<article>
<h2 class="title"><a href="/blog/2012/12/19/how-i-test-part-ii/">How I test part II - testing models</a></h2>
<div class="meta">
<span class="date">Dec 19</span>
View
2  blog/categories/ssh/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: ssh | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/ssh/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/talks/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: talks | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/talks/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
30 blog/categories/tdd/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: TDD | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/tdd/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
@@ -14,6 +14,34 @@
<entry>
+ <title type="html"><![CDATA[How I test part III: Why rspec?]]></title>
+ <link href="http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/"/>
+ <updated>2012-12-20T16:48:00+00:00</updated>
+ <id>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii</id>
+ <content type="html"><![CDATA[<p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing -- ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don't know exactly what you're testing (I confess that I like Test::Unit more because it's simpler for developers to read -- assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation -- the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO -- yup, that's right. If you have features that you want to implement later on, just add a "pending" spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it's not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I'm really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here's an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I'm abiding by this rule from the last post:</p>
+
+<p>"- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long."</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought... why bother, exactly? It's better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+]]></content>
+ </entry>
+
+ <entry>
<title type="html"><![CDATA[How I test part II - testing models]]></title>
<link href="http://luisalima.github.com/blog/2012/12/19/how-i-test-part-ii/"/>
<updated>2012-12-19T10:17:00+00:00</updated>
View
18 blog/categories/tdd/index.html
@@ -98,6 +98,24 @@
<section class="archives"><h1 class="year">2012</h1>
<article>
+ <h2 class="title"><a href="/blog/2012/12/20/how-i-test-part-iii/">How I test part III: Why rspec?</a></h2>
+ <div class="meta">
+ <span class="date">Dec 20</span>
+ <span class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</span>
+
+ </div>
+</article>
+
+
+
+
+<article>
<h2 class="title"><a href="/blog/2012/12/19/how-i-test-part-ii/">How I test part II - testing models</a></h2>
<div class="meta">
<span class="date">Dec 19</span>
View
2  blog/categories/ted/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: ted | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/ted/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
30 blog/categories/testing/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: testing | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/testing/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
@@ -14,6 +14,34 @@
<entry>
+ <title type="html"><![CDATA[How I test part III: Why rspec?]]></title>
+ <link href="http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/"/>
+ <updated>2012-12-20T16:48:00+00:00</updated>
+ <id>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii</id>
+ <content type="html"><![CDATA[<p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing -- ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don't know exactly what you're testing (I confess that I like Test::Unit more because it's simpler for developers to read -- assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation -- the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO -- yup, that's right. If you have features that you want to implement later on, just add a "pending" spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it's not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I'm really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here's an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I'm abiding by this rule from the last post:</p>
+
+<p>"- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long."</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought... why bother, exactly? It's better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+]]></content>
+ </entry>
+
+ <entry>
<title type="html"><![CDATA[How I test part II - testing models]]></title>
<link href="http://luisalima.github.com/blog/2012/12/19/how-i-test-part-ii/"/>
<updated>2012-12-19T10:17:00+00:00</updated>
View
18 blog/categories/testing/index.html
@@ -98,6 +98,24 @@
<section class="archives"><h1 class="year">2012</h1>
<article>
+ <h2 class="title"><a href="/blog/2012/12/20/how-i-test-part-iii/">How I test part III: Why rspec?</a></h2>
+ <div class="meta">
+ <span class="date">Dec 20</span>
+ <span class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</span>
+
+ </div>
+</article>
+
+
+
+
+<article>
<h2 class="title"><a href="/blog/2012/12/19/how-i-test-part-ii/">How I test part II - testing models</a></h2>
<div class="meta">
<span class="date">Dec 19</span>
View
2  blog/categories/thin/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: thin | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/thin/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/verbose/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: verbose | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/verbose/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/vnc/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: vnc | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/vnc/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/webdev/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: webdev | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/webdev/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
2  blog/categories/webrick/atom.xml
@@ -4,7 +4,7 @@
<title><![CDATA[Category: webrick | Entreprevelopment adventures]]></title>
<link href="http://luisalima.github.com/blog/categories/webrick/atom.xml" rel="self"/>
<link href="http://luisalima.github.com/"/>
- <updated>2012-12-19T19:58:35+00:00</updated>
+ <updated>2012-12-20T16:59:55+00:00</updated>
<id>http://luisalima.github.com/</id>
<author>
<name><![CDATA[Luisa Lima]]></name>
View
61 blog/page/2/index.html
@@ -7,7 +7,7 @@
<meta name="author" content="Luisa Lima">
- <meta name="description" content="Yes, today I am in &#8220;documentation&#8221; mode, which means &#8220;bloggation&#8221; mode :-) Just installed this gem &#8211; Better errors. It &hellip;">
+ <meta name="description" content="&#8230; and better yet: in the command line. No more messing around with slooow browsers in the Pi. First, install mplayer if you don&#8217;t &hellip;">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
@@ -95,6 +95,65 @@
<article class="post">
<h2 class="title">
+ <a href="/blog/2012/12/13/grooveshark-media-center-with-raspberry-pi/">
+
+ Grooveshark Media Center With Raspberry Pi</a>
+ </h2>
+ <div class="entry-content">
+ <p>&#8230; and better yet: in the command line. No more messing around with slooow browsers in the Pi.</p>
+
+<p>First, install mplayer if you don&#8217;t already have it:</p>
+
+<pre><code> sudo apt-get install mplayer </code></pre>
+
+
+<p>Then, open ~/.mplayer/config and <a href="http://martin.ankerl.com/2006/06/10/pimp-my-mplayer/">pimp your player</a> by adding the following settings:</p>
+
+<pre><code> cache=8192
+cache-min=4 </code></pre>
+
+
+<p>Next, clone the <a href="https://github.com/drakedevel/gsclient">gsclient plugin</a> by <a href="https://github.com/drakedevel">drakedevel</a>:</p>
+
+<pre><code>
+git clone https://github.com/drakedevel/gsclient.git</code></pre>
+
+
+<p>And now&#8230; RoCk and RoLL :-)</p>
+
+
+
+ </div>
+
+
+<div class="meta">
+ <div class="date">
+
+
+
+
+
+
+
+
+
+
+
+<time datetime="2012-12-13T12:09:00+00:00" pubdate data-updated="true">Dec 13<span>th</span>, 2012</time></div>
+ <div class="tags">
+
+
+ <a class='category' href='/blog/categories/grooveshark/'>grooveshark</a>, <a class='category' href='/blog/categories/raspberrypi/'>raspberrypi</a>
+
+
+</div>
+
+</div></article>
+
+
+ <article class="post">
+ <h2 class="title">
+
<a href="/blog/2012/12/13/better-errors-gem/">
Better Errors Gem</a>
View
120 index.html
@@ -7,7 +7,7 @@
<meta name="author" content="Luisa Lima">
- <meta name="description" content="Testing models From rails guides: &#8220;Ideally, you would like to include a test for everything which could possibly break. It’s a good practice &hellip;">
+ <meta name="description" content="Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all &hellip;">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
@@ -95,6 +95,65 @@
<article class="post">
<h2 class="title">
+ <a href="/blog/2012/12/20/how-i-test-part-iii/">
+
+ How I Test Part III: Why Rspec?</a>
+ </h2>
+ <div class="entry-content">
+ <p>Why RSpec? That is a good question. My main reason for using RSpec right now is because I want to have a testing + documentation + TODO bundle, all in one, like a shampoo:</p>
+
+<ul>
+<li>testing &#8211; ok, RSpec does make things a tad more complicated for testing. I believe that testing actually makes you learn more about what you code, and RSpec, being a DSL, can make things esoteric enough that sometimes you don&#8217;t know exactly what you&#8217;re testing (I confess that I like Test::Unit more because it&#8217;s simpler for developers to read &#8211; assert that this gives this result). But, on the other hand, you have shoulda! :-)</li>
+<li>documentation &#8211; the exact same thing that makes testing a bit more esoteric, makes documentation a piece of cake. You want to know how something works? Just read the tests. And RSpec does make that side of testing much clearer.</li>
+<li>TODO &#8211; yup, that&#8217;s right. If you have features that you want to implement later on, just add a &#8220;pending&#8221; spec with the description of what you want to do. Of course that you can do that in Test::Unit as well, but it&#8217;s not as beautiful and immediate as in RSpec.</li>
+</ul>
+
+
+<p>Of course that I&#8217;m really just beginning and I might change my mind eventually. <a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">Even the creator of Rails argues against RSPec</a>, and there are quite a few arguments against it (if you missed the link, here&#8217;s an <a href="http://objectreload.com/articles/2010/09/thoughts-on-testing-part-1.html">excellent blog post on that</a>).</p>
+
+<p>By the way, I&#8217;m abiding by this rule from the last post:</p>
+
+<p>&#8221;- Keep things flat — deeply nested contexts are ugly as they hinder readability of your test cases. Split your tests up into different files if they’re getting too long.&#8221;</p>
+
+<p>I was trying to make things DRY in the tests, and then I thought&#8230; why bother, exactly? It&#8217;s better if they are more readable, for the sake of documentation as stated above. Amen, brothers.</p>
+
+<h2>Why not Cucumber for request specs?</h2>
+
+<p>All the reasons are in this <a href="http://epimetrics.com/entries/3129">excellent post</a>.</p>
+
+
+
+ </div>
+
+
+<div class="meta">
+ <div class="date">
+
+
+
+
+
+
+
+
+
+
+
+<time datetime="2012-12-20T16:48:00+00:00" pubdate data-updated="true">Dec 20<span>th</span>, 2012</time></div>
+ <div class="tags">
+
+
+ <a class='category' href='/blog/categories/tdd/'>TDD</a>, <a class='category' href='/blog/categories/rails/'>rails</a>, <a class='category' href='/blog/categories/rspec/'>rspec</a>, <a class='category' href='/blog/categories/testing/'>testing</a>
+
+
+</div>
+
+</div></article>
+
+
+ <article class="post">
+ <h2 class="title">
+
<a href="/blog/2012/12/19/how-i-test-part-ii/">
How I Test Part II - Testing Models</a>
@@ -699,65 +758,6 @@ <h2 class="title">
</div></article>
-
- <article class="post">
- <h2 class="title">
-
- <a href="/blog/2012/12/13/grooveshark-media-center-with-raspberry-pi/">
-
- Grooveshark Media Center With Raspberry Pi</a>
- </h2>
- <div class="entry-content">
- <p>&#8230; and better yet: in the command line. No more messing around with slooow browsers in the Pi.</p>
-
-<p>First, install mplayer if you don&#8217;t already have it:</p>
-
-<pre><code> sudo apt-get install mplayer </code></pre>
-
-
-<p>Then, open ~/.mplayer/config and <a href="http://martin.ankerl.com/2006/06/10/pimp-my-mplayer/">pimp your player</a> by adding the following settings:</p>
-
-<pre><code> cache=8192
-cache-min=4 </code></pre>
-
-
-<p>Next, clone the <a href="https://github.com/drakedevel/gsclient">gsclient plugin</a> by <a href="https://github.com/drakedevel">drakedevel</a>:</p>
-
-<pre><code>
-git clone https://github.com/drakedevel/gsclient.git</code></pre>
-
-
-<p>And now&#8230; RoCk and RoLL :-)</p>
-
-
-
- </div>
-
-
-<div class="meta">
- <div class="date">
-
-
-
-
-
-
-
-
-
-
-
-<time datetime="2012-12-13T12:09:00+00:00" pubdate data-updated="true">Dec 13<span>th</span>, 2012</time></div>
- <div class="tags">
-
-
- <a class='category' href='/blog/categories/grooveshark/'>grooveshark</a>, <a class='category' href='/blog/categories/raspberrypi/'>raspberrypi</a>
-
-
-</div>
-
-</div></article>
-
<nav id="pagenavi">
View
8 sitemap.xml
@@ -67,11 +67,15 @@
<lastmod>2012-12-19T19:58:27+00:00</lastmod>
</url>
<url>
+ <loc>http://luisalima.github.com/blog/2012/12/20/how-i-test-part-iii/</loc>
+ <lastmod>2012-12-20T16:59:40+00:00</lastmod>
+ </url>
+ <url>
<loc>http://luisalima.github.com/blog/archives/</loc>
- <lastmod>2012-12-19T19:58:27+00:00</lastmod>
+ <lastmod>2012-12-20T16:59:40+00:00</lastmod>
</url>
<url>
<loc>http://luisalima.github.com/</loc>
- <lastmod>2012-12-19T19:58:27+00:00</lastmod>
+ <lastmod>2012-12-20T16:59:40+00:00</lastmod>
</url>
</urlset>
Please sign in to comment.
Something went wrong with that request. Please try again.