<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Parallel on Random Musings</title><link>https://chengl.com/tags/parallel/</link><description>Recent content in Parallel on Random Musings</description><generator>Hugo</generator><language>en-us</language><copyright>Cheng Long</copyright><lastBuildDate>Sun, 30 Jul 2017 08:58:05 +0000</lastBuildDate><atom:link href="https://chengl.com/tags/parallel/index.xml" rel="self" type="application/rss+xml"/><item><title>Life is Short. Run Tests in Parallel</title><link>https://chengl.com/post/life-is-short-run-tests-in-parallel/</link><pubDate>Sun, 20 Mar 2016 08:56:00 +0000</pubDate><guid>https://chengl.com/post/life-is-short-run-tests-in-parallel/</guid><description>&lt;p&gt;If you are doing Rails, chances are that you have &lt;a href="http://rspec.info/"&gt;RSpec&lt;/a&gt; and &lt;a href="https://cucumber.io/"&gt;Cucumber&lt;/a&gt; tests. They are great tools to give you the confidence that your software is working as expected. But as project grows, you may find that your tests are getting slower and slower, expecially the Cucumber tests. It not only slows down the speed of your local development, but also your Continuous Integration pipeline (Test is probably the first stage in your CI). We don&amp;rsquo;t want to waste time waiting tests to finish in either local or CI. We want to develop and integrate faster. Here is how.&lt;/p&gt;</description></item></channel></rss>