https://www.tkalin.com/tags/rspec/ Recent content in rspec on Ivan Tkalin Hugo -- gohugo.io en-us itkalin@gmail.com (Ivan Tkalin) itkalin@gmail.com (Ivan Tkalin) © Ivan Tkalin Sun, 26 Apr 2015 15:00:00 +0000 https://www.tkalin.com/blog_posts/upgrading-to-rspec3/ Sun, 26 Apr 2015 15:00:00 +0000 itkalin@gmail.com (Ivan Tkalin) https://www.tkalin.com/blog_posts/upgrading-to-rspec3/ This short article is TL;DR of the talk: RSpec 3 and why I expect(you).to care by Jon Rowe. I picked 3 important recommendations out of this talk which I’m going to follow. 1. Use zero monkey patching mode This will completely disable all the monkey patching and will make RSpec less magical. Of course, it has a few consequences: DSL will not be exposed globally, so RSpec.describe must be used instead of describe etc. https://www.tkalin.com/blog_posts/testing-authorization-using-rspec-parametrized-shared-examples/ Wed, 23 May 2012 15:00:00 +0000 itkalin@gmail.com (Ivan Tkalin) https://www.tkalin.com/blog_posts/testing-authorization-using-rspec-parametrized-shared-examples/ I have a rails app, that uses Devise for authentication and CanCan for authorization. There is a group of controllers in my application, that should be accessible by administrators only. I was thinking about a DRY way to test these resources and their accessibility by administrators only (using request specs with RSpec and Capybara). The idea is to have shared examples, which try to visit resource url as unauthenicated user, authenicated non-privileged user and administrator, and check if desired resource was loaded or not.