I often see Cucumber features written like this:
Given I a have an account with email: "user@test.com" and password: "password" When I go to the log in page And I fill in "Email" with "user@test.com" And I fill in "Password" with "password" And I press "Log in" Then I should see "Logged in successfully." And I should not see "Log in"
It works and does the job but I feel that it isn’t enough. It’s fragile in several ways.
When writing a cucumber feature that involves pagination, the easiest thing to do is to create the required number of objects to generate pagination.
Given 31 tasks exist # pagination defaults to 30
The downside of course is speed. Creating a large number of complex objects can add a lot of extra wait time to your cucumber runs. In my case, although I only had a few scenarios that involved pagination, my per_page setting was 50 and the objects I was creating were complex. The end result was a extra couple of (unnecessary) minutes. It wasn’t too bad so I left myself a TODO to fix it one day and that day finally came.
I discovered the web back in the mid 90‘s when Netscape was the new kid on the block. I’ve made a couple of sites, worked as a web admin, and now I am a Ruby on Rails programmer. But I’ve never had a blog – never felt I had anything ... Continue reading »
