Using Authlogic with Cucumber

I have been working with Cucumber lately and have been retrofitting one of my main projects Sumuv.com with appropriate behavioral tests.  We have a fully functional test suite written with Shoulda and Test::Unit, so I am not particularly interested in translating the unit and functional tests to RSpec.

This is the vegetable you are looking for.

I figured that since the Cucumber BDD tests are completely different than the Shoulda unit and functional tests, I could just slip my Cucumber steps right on in.  It does seem a little strange to be writing the functional tests in Test::Unit and the behavioral steps in RSpec.  In the future I will probably follow the Shoulda train and move to RSpec exclusively, but I am enjoying the differences in the two platforms on this particular retrofit.

While I am mentioning the Shoulda train, I really enjoyed Thoughtbot’s post “This should_change Your Mind“.  Their very simple explanations of the difference between behavioral testing and functional testing created a clear distinction in my mind.  It was the golden nugget of wisdom I had been looking for.

I have been a big fan of Binary Logic’s Authlogic gem for handling site authentication and user sessions.  I love the clean interface and versatility.  A lot of forethought went in to make this an elegant interface on top of some pretty robust and secure code.

As a result of this work, I have created a set of Authlogic behavior steps to use in my Cucumber tests.  These steps cover most of your basic functionality and provide some helper functions that you can use in your other step definitions.  The Cucumber feature definitions cover the major elements of authentication: logging in, logging out and the presence of a UserSession.

I will continue to improve the quality and coverage of these features.  I plan to include a set of features to cover user registration.  I offer this here because I find it useful for my other projects.  If you find it helpful too, please let me know!

http://github.com/mindtonic/AuthLogic-Cucumber-Steps

Webrat for integration testing

Webrat:

• http://github.com/brynary/webrat/tree/master
• http://gitrdoc.com/brynary/webrat/tree/master
• http://codese.wordpress.com/2009/02/05/using-shoulda-webrat-to-write-integration-tests-for-rails/
• http://blog.bitmacro.com/2008/11/14/shoulda-factory_girl-webrat

Integration Testing:

• http://weblog.jamisbuck.org/2006/3/9/integration-testing-in-rails-1-1
• http://www.martinfowler.com/articles/continuousIntegration.html
• http://api.rubyonrails.org/classes/ActionController/Integration/Session.html
• http://locomotivation.squeejee.com/post/109227509/ruby-on-rails-integration-testing-with-integrity
• http://ajaxonrails.wordpress.com/2006/11/02/integration-testing-in-ruby-on-rails-how-to-maintain-sessions-while-testing-in-rails/
• http://bhanoo.blogspot.com/2007/09/rails-integration-testing.html
• http://blog.danielwellman.com/2008/06/writing-rails-integration-tests-with-webrat.html
• http://6brand.com/rails-integration-testing-how-to-learn.html

should_eventually write this test

One thing I liked about rspec was the ability to define tests that you had not yet written. That way you could remind yourself when running the test suite that there are things still to do. Previously in Shoulda, I have been writing these kinds of tests in all caps and using “assert false” to trigger failure and remind me of future work. Turns out there is a nifty way to do it with Shoulda. (I should have guessed there would be!)

should_eventually "do something"

#or just leave off the block
should "do something"

Thanks to BlenderBox for bringing this to my attention while researching Shoulda integration testing.

Unit Testing Object Oriented PHP5 Code

I have been doing a lot for work with testing and development in Ruby. This has lead me to want to find an option to write Unit Tests for my own PHP based Content Management System, Shabda. It would be a very wise move to make sure that the core system files function exactly as expected. I will update this blog post as I go along.

My research has yielded two possible testing options:

• PHPUnit
• SimpleTest

SimpleTest

Other blogs with more information: http://vailo.wordpress.com/2008/07/03/php-unit-test-test-driven-development/