In a model spec, I’ll generally have expectations for validations and any non-trivial class or instance methods.
This is one of the reasons it’s a good idea to move logic out of the controller and into the model (or maybe a service object)-it’s much easier to test that way. Model tests-unlike controller and feature tests-don’t require much environment setup or mocking. If you’re familiar with unit testing, testing Rails models isn’t much different. In addition to those, while not covered here, you might also decide to write unit tests for other parts of your app: Acceptance) Specs Test your Rails app from the browser as a user-use cases, interactions, and maybe even some JavaScript spec/features/post_management_spec.rb In this article, we’ll write tests that touch on each part of the Rails MVC architecture: Model Specs Test your Rails models-scopes, validations, custom methods spec/models/post_spec.rb Controller Specs Test your Rails controllers-CRUD, requests, sessions, param shuffling, formats spec/controllers/posts_controller_spec.rb Feature (a.k.a. The real objective isn’t to hit some arbitrary percentage-it’s to make your app more reliable for your users and prevent regressions as you develop it. Likewise, while getting to 100% coverage is a noble goal, it isn’t always as realistic (in the face of schedule and budget constraints) or as helpful (think: future refactoring) as it might seem. If you find that a test requiring extensive mocking or brittle networking logic begins taking up more than its share of your development time, in my book it’s fine to just git rm it and move on. When I’m testing a Rails app, my goal is to get the most bang for my buck-that is, the most test coverage for the fewest lines of test code. In Part 2, with the setup out of the way, we’ll dive into writing tests for the various components of a Rails app.īefore diving in, I will say that some of this may be a bit opinionated. If you missed Part 1, head over to Testing Rails 4 Apps With RSpec 3: Part I to get caught up first. It "should get the first job in the queue for the Cheat Cheat" = FactoryGirl.In this two-part series, I cover testing a Rails application using RSpec and some other popular gems. Undefined local variable or method `app' for #Īnybody has an idea of what's going on here?ĮDIT: Here's the test: describe "#new" do I get this error message: Failure/Error: r = JSON.parse(last_response)
I have my Rspec Example that does just fine until this line: r = JSON.parse(last_response) Require File.expand_path("././config/environment", _FILE_) I followed the instructions and here is my spec_helper.rb file require 'rack/test'Īnd here is my rails_helper file: ENV ||= 'test' I want to test a controller using the rask-test last_response method. I've been working on a Rails 4.1.1 app and I am setting up Rspec.
0 kommentar(er)
