What is Better Specs Better Specs is a collection of best practices developers learned while testing apps that you can use to improve your coding skills, or simply for inspiration. Better Specs came to life at Lelylan (open source IoT cloud platform) and checking out its test suite may be of inspiration. Better Specs focus on Rails testing, but our goal is to create testing guidelines covering mos
rspec-2.11 がリリースされましたね。いくつかの変更点の中に、今後は should ではなく expect を推奨し、デフォルトでは expect のみが有効化されるようになる、というものがありました。 http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax 個人的にこの変更は説得力に欠けるなーと思っていて、 expect 推しにする理由が should は Kernel にはえるので Kernel を include しない BasicObject のインスタンスに対して should を呼ぶとおかしくなる 標準ライブラリ delegate は Kernel のメソッドの一部だけを include するので rspec と delegate のどちらが先にロードされるかによって should の挙動
I watch a lot of tests run in a given day. So I figured why not make it more fun. Inspired by minitest’s pride, and um cats? I came up with a Nyan Cat inspired RSpec formatter. Update: After last week’s launch, Nyan Cat received a great response from the Ruby world. Over the weekend, I released version 0.0.2. It includes a few bug fixes and some really cool enhancements. Most notably, Nyan Cat now
We released RSpec-2.8.0 today with a host of new features and improvements since 2.7. Some of the highlights are described below, but you can see the full changelogs at: http://rubydoc.info/gems/rspec-core/file/Changelog.md http://rubydoc.info/gems/rspec-expectations/file/Changelog.md http://rubydoc.info/gems/rspec-mocks/file/Changelog.md http://rubydoc.info/gems/rspec-rails/file/Changelog.md Docu
Use shared_context to define a block that will be evaluated in the context of example groups either explicitly, using include_context, or implicitly by matching metdata. shared_context "shared stuff", :a => :b do before { @some_var = :some_value } def shared_method "it works" end let(:shared_let) { {'arbitrary' => 'object'} } subject do 'this is the subject' end end require "./shared_stuff.rb" des
I opened up my twitter client this afternoon and I saw "54 Messages, 28 Mentions". I tell you honestly, the first thought I had was: my twitter account had been hacked. Then I started to comb through the messages and I found out what happened. It all started with a tweet from Joe Fiorini. We both worked together on a large Rails application. The application was a little light on tests, so I asked
Yay! I got vim and autotest integration working. When I run autotest, if there is an error, I can have Vim read the errors from autotest and jump me to the right place. Here is a video of me using it: Please note that I'm not copying and pasting anything. In vim, I hit a command and Vim automatically picks up errors from autotest and jumps me to the line where the error occurred. You too can impr
RSpec-2.0.0 has been released! This marks the end of a year-long effort that improves RSpec in a number of ways, including modularity, cleaner code, and much better integration with Rails-3 than was possible before. Docs, with a little bit of relish In addition to the documentation available at all the places mentioned my earlier post, we’ve also got all of the Cucumber features posted to Justin K
Ruby Weekly is a weekly newsletter covering the latest Ruby and Rails news. 9 months in the making comes RSpec 2.0, the latest major version of Ruby's most popular behavior driven development (BDD) framework (now at a gem install rspec near you). Kudos to the 82 contributors and RSpec's team lead, David Chelimsky. What has RSpec 2.0 got that RSpec 1.x doesn't? Modularity. RSpec has been split up i
The state of Test Driven Development For the latest version of this information go here and get the article that grew out of this post Test Driven Development (TDD) has made it to prime time. Big companies are paying big money to have their programmers trained in how to do TDD. It’s a popular topic at conferences… agile and otherwise. My book on TDD won a Jolt award. So everything’s rosy, huh? Eve
前回の続き Cucumberは巨大で多くのコンポーネントの集合体です。また構成もいくつか種類があり、試験対象のアプリケーションによって時に構成を変える必要があります。今回はCucumberの構成についてまとめ、選択肢について簡単に解説していきたいと思います。 まずはCucumberの依存関係を覗いてみましょう。アウトラインを把握するだけのためで、構成の選択肢とは関係ありません。 $ gem dependency cucumber --version 0.6.2 --remote Gem cucumber-0.6.2 term-ansicolor (>= 1.0.4, runtime) #標準出力に色をつける treetop (>= 1.4.2, runtime) #Ruby用の構文解析器生成系の一つ polyglot (>= 0.2.9, runtime) builder (>= 2.1.
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く