A developer's journey through BrowserCms.

Thursday, April 4, 2013

It would help to check Capybara output!

I was battling with my cucumber tests recently. The problem was that the wrong user was being setup for the tests. I was seeing 'unauthorized access' in Firefox (WebDriver). Also, WebDriver's activity is logged in 'logs/test' and that was reporting unauthorized access as well.

Sure enough, I was mistaking 'registered user' for an authorized user. A registered user does not have special editing and publishing permissions (at least for vanilla BrowserCms).

When I correctly assigned the user login, I got a little further.

Ok; almost there. The remaining issue was that my cmsuser account is getting truncated after the first test. That explains why the first scenario works and the others don't.

Finally, tests are passing again.

./bin/cucumber -r features --drb features/pages.feature

Project cucumber features

No comments:

Post a Comment