When I create a post, I pass in a hash of the fields I'd like to fill in.When I create a post, I'm using a View module so that it won't use the ActiveRecord object.I'm directly using Capybara's dsl to navigate.Let's take a look at a few interesting things: :title => 'View abstraction in integration tests',Īssert_equal 'View abstraction in integration tests',Īssert_equal 'We must go deeper', View:: Post Test for a simple blog site # Given I am on the posts page One of the major goals of this implementation is to make it easy to interact with the UI and objects within it. I was confident enough in the solution that I decided to just use Test::Unit and Capybara to write my test code. I decided to implement the Bridge Pattern in my integration tests. So, I recently had to write some integration tests from scratch, and I decided to do something different.
#Postview integration pints or nodes code
Brittleness introduced by coding html and css structure into test code that prevents refactoring the view.Cumbersome to check the view for expected output, often resulting in lots of css selectors.Often resulting in global variables used between steps Hard to reference objects throughout Cucumber scenarios.Here are some pain points I've felt while writing integration tests in the past: But that's all I've ever seen (disclaimer: I am young, and have much to learn). Internally, many frameworks use the Visitor pattern to execute the tests. Most of us use the Factory pattern through a variety of gems. However, there is one thing that I don't see much of in tests: Object-Oriented Patterns. There is no doubt in my mind that these frameworks have made testing easier by adding lots of common actions, and allowing you to define your own common actions. RSpec is global by nature, there are no test classes, just describe blocks. There is a single, global, collection of steps. Cucumber is designed so that each scenario has a set of steps. Ruby on Rails has a bunch of popular of test frameworks, such as:īut one common aspect to all of the frameworks, out of the box, is that they're very procedural. Goal: Make integration tests drier by adding a view abstraction layer
0 kommentar(er)
