{"provider_url":"https://hatena.blog","type":"rich","width":"100%","author_name":"shinkufencer","url":"https://shinkufencer.hateblo.jp/entry/2020/08/19/232152","published":"2020-08-19 23:21:52","blog_title":"\u30b3\u30fc\u30c9\u65e5\u9032\u6708\u6b69","blog_url":"https://shinkufencer.hateblo.jp/","description":"\u5909\u5316\u306e\u7d4c\u7def\u304c\u306a\u308b\u307b\u3069\u306a\u30fc\u3068\u601d\u3063\u305f\u306e\u3067\u307e\u3068\u3081\u308b\u3002 \u51fa\u5178 Notable Changes in RSpec 3 \u89e3\u8aac RSpec3\u306e\u30ea\u30ea\u30fc\u30b9\u30ce\u30fc\u30c8\u3044\u308f\u304f RSpec 2 had a pair of matchers (be_true and be_false) that mirror Ruby's conditional semantics: be_true would pass for any value besides nil or false, and be_false would pass for nil or false. In RSpec 3, we've renamed these \u2026","image_url":null,"version":"1.0","height":"190","title":"RSpec3\u3067be_true\u3068be_false\u306f\u306a\u304f\u306a\u308a\u3001be_truthy\u3068be_falsey(be_falsy)\u306b\u306a\u3063\u305f","categories":["RSpec"],"provider_name":"Hatena Blog","author_url":"https://blog.hatena.ne.jp/shinkufencer/","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fshinkufencer.hateblo.jp%2Fentry%2F2020%2F08%2F19%2F232152\" title=\"RSpec3\u3067be_true\u3068be_false\u306f\u306a\u304f\u306a\u308a\u3001be_truthy\u3068be_falsey(be_falsy)\u306b\u306a\u3063\u305f - \u30b3\u30fc\u30c9\u65e5\u9032\u6708\u6b69\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>"}