I originally created my VM with 20GB of disk space under the false impression that my image file would grow automatically as more space was required. After using the VM for sometime I realised that 20GB was not going to be enough and that I was going to need more space. The question was how do I increase the size without having to create the VM from scratch, not a task I relished as I’d spent many hours using the VM and had installed a lot of software and really did not want to repeat the process.

I used Google to search for how I could achieve this thinking that a lot of people would strike this problem and that a solution would be but a few clicks away…wrong! After a lot of searching I found a few articles on how this could be achieved, a lot of them where complicated including having to hack the MBR. After making a backup of my image file, I tried a couple of solutions but they ended up damaging my image file to the point where I could no longer boot the VM.

It’s at this point I started to sweat, I had spent hours installing and setting up software within my VM, I really did not want to have to do it all over again! After a lot of experimentation I found something that works reliably for me, I’m sure there are better ways of doing this (is’nt there always!) but this works for me every time.

DISCLAIMER: Take care in what you do, make sure you have a reliable backup of the VM image before you start. You do this at your own risk, I accept no responsibility if it all goes wrong.

So let’s dive in…

Step 1: Stop the VM

Step 2: Change to the directory where your VM image files are stored, mine is in /kvm/ubuntu-dev/

cd /kvm/ubuntu-dev

Here is what my 20GB file looks like.

Step 3: Backup the image file, my image file is called ubuntu-dev.img. I created a sub-directory called bak where I store my image backup file

sudo cp ubuntu-dev.img bak/ubuntu-dev.img.bak

Step 4: Create a blank qemu file, this is the file we will be adding to our VM image. Create it with a size equal to the amount of extra disk space you want added to your VM. In my case I want to add an additional 30GB of space.

sudo qemu-img create -f raw addon.raw 30G

This is what the addon file looks like on my system after it is created.

Step 5: Rename the original image file to .save as is shown in the image above. We never actually modify the original image file so we end up with two backup files, the .save as well as the backup file we created in Step 3, just in case something goes wrong. When you are sure everything has worked you can always delete these files.

Step 6: We are now ready to combine the image file with the new blank qemu file we created earlier. You need to be logged in as the super user to perform this step.

su

cat ubuntu-dev.img.save addon.raw >> ubuntu-dev.img

Step 7: Once this completes you can check the new file size, my new file size is now 50GB which is my original 20GB + 30GB of extra space.

Step 8: We have successfully increased the size of our image file by 30GB to 50GB, now we need to fix our partitions. To do this you need to downloaded GParted and create a live CD. Once you have created the CD and loaded into your machine run the following command to start GParted using the new image file.

sudo qemu -hda ubuntu-dev.img -cdrom /dev/cdrom -boot d

The following window should be displayed.

Select the "GParted Live (Default settings)" option or the one appropriate for you. You will then be prompted with a number of setup options, I normally accept the defaults. Once GParted has been loaded you should see your current VM image partitions, here is mine:

The first thing we need to do is delete the swap partition so that the primary ext3 partition is next to the new unallocated space we added, this will allow us to expand the primary partition. Note that the correct device is selected in the top right hand corner, it shows our newly expanded 50GB device.

So select the swap partition and select "Delete", the command will be added to the pending operations list shown in the bottom panel. We can undo all operations until we select "Apply".

Now we can resize the primary partition, select primary partition and select "Rezise/Move" and resize the partition as required. I’m reserving 2GB for the swap partition and allocate the rest to the primary partition.

The last step is to create a new swap partition.

We have now completed all the steps required to re-partition our image. We deleted the old swap partition, resized the primary partition and created a new swap partition. All these steps are listed as pending actions, we can still undo anything at this stage but I’m happy with what I’ve done and select "Apply" to get GParted to make the changes.

 GParted will then start making the changes.

Once completed we can see our new partitions, the primary partition is now 48GB in size and we have a 2GB swap partition.

Step 9: Exit GParted and restart your system, my VM automatically starts when the server is restarted. Login to the VM (hopefully everything starts ok). We need to activate the swap file in the new swap partition we created, so once you have logged in start GParted, your new partitions should be displayed.

 To activate the swap file, select the swap partition and press the right mouse button. The following popup menu should be displayed, select the "Swapon" option to turn the swap file on.

Conclusion

That’s it we have successfully added and extra 30GB of space to our VM image file. Once you are happy that everything is working you can remove your backup files. I normally keep mine for a little while until I’m 100% sure everything is working as it should.

• machinist - After trying many fixture replacement plugins I’m happy with machinist, so far it does everything I need.
• forgery - Machinist includes Sham which allows me to create dummy data for my fixtures, I use forgery which is a very nice fake data generator to supply the data to Sham,
• cucumber - Is the replacement for rspec user stories, it allows you to write plain text stories (features) and execute them as functional tests.
• webrat - It lets you write expressive and robust acceptance tests for a Ruby web application.
• rspec - Is a Behaviour Driven Development (BDD) framework for writing executable code examples.

After reading lot’s of articles and looking at lots of example code I was finding it all very daunting, I found myself suffering from a severe case of coders block. I really did not know where to start, how to structure my code, how to write the features and so on. I was hoping that the Rspec book might have been released before I had to start development to give me some direction but the beta release has been delayed and I had to face my fears and dive in.

Once I started, I was pleasantly surprised how natural the whole process felt, after writing my first half dozen features or so I was really starting to enjoy it! In this article I want to give a brief overview of what I did to get started, show some example features and steps, as well as demonstrating how all the tools in my toolkit mesh together to form a very nice testing framework. I’m still very new to the process of writing features and steps and am still becoming familiar with all the tools, so I’m sure that I will make adjustments as I become more experienced in using the framework.

I will not go into how to install the plugins as this is well documented for each plugin.

Creating my fixtures

I create my fixtures using machinist. To use machinist you use a class method called blueprint which is an extension of ActiveRecord::Base which means you can use it on any of your ActiveRecord models. In my application I have an "Account" link that allows the user to modify their account details including the password and email address which is the first feature I wanted to write. So the first thing I did was to create some blueprints for my user models in the blueprint.rb file which resides in the spec directory. The first thing I do is define some standard sham’s that I will use in my blueprints, I use forgery to populate these shams with some good dummy data.

require ‘forgery’

# Shams
# We use forgery to make up some test data

Sham.name  { NameForgery.full_name }
Sham.login  { InternetForgery.user_name }
Sham.email  { InternetForgery.email_address }
Sham.password  { BasicForgery.password }
Sham.string { BasicForgery.text }
Sham.text { LoremIpsumForgery.text }

# Blueprints

Role.blueprint do
  name { ‘guest’ }
end

SiteUser.blueprint do
  user_type { ‘SiteUser’ }
  login { Sham.login }
  name { Sham.name }
  email = Sham.email
  email { email }
  email_confirmation { email }
  pwd = Sham.password
  password { pwd }
  password_confirmation { pwd }
  accept_terms { ‘true’ }
  time_zone { ‘Melbourne’ }
end

OpenidUser.blueprint do
  user_type { ‘OpenidUser’ }
  time_zone { ‘Melbourne’ }
  email { Sham.email }
end

These blueprints allow me to easily create some objects using make, i.e.

user = SiteUser.make

Where to put my test files

There are any number of ways to structure your files and directories, after reading this article I decided to create a new sub-directory for each model that I wanted to test, so my directory structure looks something like this:

So for model User I created a users directory which contains a user.feature file and a steps_definitions sub-directory where the step files will be located, in this case we have user-steps.rb.

Setting up my env.rb

Before we start writing features we need to tweak the cucumber env.rb file. I’ve added code to load webrat and machinist, my file looks like this:

# Sets up the Rails environment for Cucumber
ENV["RAILS_ENV"] = "test"
require File.expand_path(File.dirname(__FILE__) + ‘/../../config/environment’)
require ‘cucumber/rails/world’
Cucumber::Rails.use_transactional_fixtures

# Add webrat
require "webrat"
Webrat.configure do |config|
  config.mode = :rails
end

# Comment out the next line if you’re not using RSpec’s matchers (should / should_not) in your steps.
require ‘cucumber/rails/rspec’

# Add machinist
require File.join(RAILS_ROOT, ’spec’, ‘blueprints’)

Writing my first feature

The first feature I wanted to write was the ability for the user to display their account details once they had logged in. I initially started writing the feature using my own words to describe it, for example:

Feature: User functions

In order to maintain the correct account information
As a logged in user
I want to maintain my account information

Scenario: Display my account information if I am an SiteUser
  Given I am logged in as a SiteUser
  When I go to the "Account" page
  Then I should see my account details
    And I should see a "Change Password" link
    And I should see "Change Email" link

I then implemented each of these in my steps file using webrat. It’s only after some time that I realized that cucumber comes with a webrat steps definition file, i.e. webrat_steps.rb. Which contains a lot of standard webrat steps which I could directly call from my feature definition. So I could rewrite my scenario using the webrat steps:

Scenario: Display my account information if I am an SiteUser
  Given I am logged in as a SiteUser
  When I follow "Account"
  Then I should see "Account"
    And I should see my account details
    And I should see "Change Password"
    And I should see "Change Email"

The steps in bold are all webrat steps that I do not have to implement in my own steps file as they are implemented in the webrat steps file! There are only two steps that I have to define myself.

Step 1: Given I am logged in as a SiteUser

This step is quite involved as I have to figure out how to login a user using a user name/password, I also need to cater for those users that use an OpenID. I decided to create a step_helper.rb file which is located in the /features/step-definitions sub-directory and will be automatically loaded by cucumber, which will contain any shared steps. It currently contains only one step that handles the login process for a user and looks like this:

# Login
# e.g.
# Given I login as a SiteUser in the guest role
# Given I login as a OpenidUser in the admin role
#
Given /I login as a (.*) in the (.*) role/i do |user_type, role|
  role = Role.make
  @user = Object::const_get(user_type).make_unsaved(:roles => role) 
  if (!@user.openid)
    @user.activate!
    visit login_path
    fill_in("login", :with => @user.login)
    fill_in("password", :with => @user.password)
  else
    # identity_url not allowed to be set via mass assignment in blueprint
    @user.identity_url = ‘https://good.openid.url/’
    @user.activate!
    visit login_with_openid_path
    fill_in("openid_identifier", :with => @user.identity_url)   
  end 
  click_button("Log in")
  Then ‘I should see "Dashboard"’
end

 To use it I create a separate step within my steps file. One important point to note is that you can reuse steps by calling them directly from within other steps. In the example below we are calling the shared login step from within the step by calling Given "I login as a #{user_type} in the guest role".

Given /I am logged in as a (.*)/i do |user_type|
   Given "I login as a #{user_type} in the guest role"
end

This step can then be used in my feature like this:

Given I am logged in as a SiteUser

Step 2: And I should see my account details

The last step we need to implement is the one that checks to make sure that the users account details are actually being displayed. The step do this looks like this:

Then /I should see my account details/ do
  Then "I should see \"#{@user.name}\""
  Then "I should see \"#{@user.company}\""
end

Running my features

Before we run the feature here is the content of our feature and step file so far.

Feature: User functions

In order to maintain the correct account information
As a logged in user
I want to maintain my account information

Scenario: Display my account information if I am an SiteUser
  Given I am logged in as a SiteUser
  When I follow "Account"
  Then I should see "Account"
    And I should see my account details
    And I should see "Change Password"
    And I should see "Change Email"

And my user-steps.rb looks like this:

Given /I am logged in as a (.*)/i do |user_type|
   Given "I login as a #{user_type} in the guest role"
end

Then /I should see my account details/ do
  Then "I should see \"#{@user.name}\""
  Then "I should see \"#{@user.company}\""
end

When I run the the feature assuming I’ve implemented the code I get the following output:

More example features

Here are a few more example features and the steps.

Feature: User functions

In order to maintain the correct account information
As a logged in user
I want to maintain my account information

Scenario: Display my account information if I am an SiteUser
  Given I am logged in as a SiteUser
  When I follow "Account"
  Then I should see "Account"
    And I should see my account details
    And I should see "Change Password"
    And I should see "Change Email"

Scenario: Display my account information if I am an OpenidUser
  Given I am logged in as a OpenidUser
  When I follow "Account"
  Then I should see "Account"
    And I should see my account details
    And I should not see "Change Password"
    And I should not see "Change Email"

Scenario: Allow me to change my password
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Password"
    And I fill in my new password details
    And I press "Change your password"
  Then my password should be changed
    And I should see "Account"
    And I should see "Password successfully updated"

Scenario: Not allow me to change my password if the old password incorrect
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Password"
    And I fill in an incorrect old password
    And I press "Change your password"
  Then my password should not be changed
    And I should see "You password was not changed, your old password is incorrect."

Scenario: Not allow me to change my password when the password and confirmation is not the same
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Password"
    And I fill in an incorrect password confirmation
    And I press "Change your password"
  Then my password should not be changed
    And I should see "New password does not match the password confirmation."

Scenario: Allow me to change my account details
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I fill in my new account details
    And I press "Save"
  Then my account details should be changed
    And I should see "Account details updated."

Scenario: Allow me to change my email
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Email"
    And I fill in my new email address
    And I press "Change your email"
  Then my email should be changed
    And I should see "Account"
    And I should see "Email successfully updated"

Scenario: Not allow me to change my email when the email and confirmation is not the same
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Email"
    And I fill in an incorrect email confirmation
    And I press "Change your email"
  Then my email should not be changed
    And I should see "New email does not match the email confirmation."

Steps in user-steps.rb

Given /I am logged in as a (.*)/i do |user_type|
   Given "I login as a #{user_type} in the guest role"
end

Then /I should see my account details/ do
  Then "I should see \"#{@user.name}\""
  Then "I should see \"#{@user.company}\""
end

When /I fill in my new password details/ do
  When "I fill in \"old_password\" with \"#{@user.password}\""
  When ‘I fill in "password" with "test_123"’
  When ‘I fill in "password_confirmation" with "test_123"’
end

When /I fill in an incorrect old password/ do
  When "I fill in \"old_password\" with \"#{@user.password + ‘xyz’}\""
  When ‘I fill in "password" with "test_123"’
  When ‘I fill in "password_confirmation" with "test_123"’
end

When /I fill in an incorrect password confirmation/ do
  When "I fill in \"old_password\" with \"#{@user.password}\""
  When ‘I fill in "password" with "test_123"’
  When ‘I fill in "password_confirmation" with "test_1234"’
end

When /I fill in my new account details/ do
  When ‘I fill in "user_name" with "Fred Flintstone"’
  When ‘I fill in "user_company" with "Acme Rocks"’
  When ‘I select "(GMT+10:00) Canberra" from "user_time_zone"’
end

Then /my password should be changed/ do
  SiteUser.find_by_id(@user.id).authenticated?(’test_123′).should == true
end

Then /my password should not be changed/ do
  SiteUser.find_by_id(@user.id).authenticated?(’test_123′).should == false
end

Then /my account details should be changed/ do
  u = SiteUser.find_by_id(@user.id)
  u.name.should == ‘Fred Flintstone’
  u.company.should == ‘Acme Rocks’
  u.time_zone.should == ‘Canberra’
end

When /I fill in my new email address/ do
  When ‘I fill in "email" with "test@isp.com"’
  When ‘I fill in "email_confirmation" with "test@isp.com"’
end

When /I fill in an incorrect email confirmation/ do
  When ‘I fill in "email" with "test@isp.com"’
  When ‘I fill in "email_confirmation" with "test123@isp.com"’
end

Then /my email should be changed/ do
  SiteUser.find_by_id(@user.id).email.should == ‘test@isp.com’
end

Then /my email should not be changed/ do
  SiteUser.find_by_id(@user.id).email.should_not == ‘test@isp.com’
end 

Feature Writing Style

There seems to be two styles that you can use when writing your features, "Imperative" and "Declarative" which is described in detail in the article Imperative vs Declarative Scenarios in User Stories written by Ben Mabey. I understand the extreme cases as demonstrated by the examples given by Ben, but what about a feature such as this one, can this be classed as being written using the Imperative style?

Scenario: Allow me to change my password
  Given I am logged in as a SiteUser
  When I follow "Account"
    And I follow "Change Password"
    And I fill in my new password details
    And I press "Change your password"
  Then my password should be changed
    And I should see "Account"
    And I should see "Password successfully updated"

Does the Imperative style dictate that all steps appear in the feature, the example above do have some steps that are defined in the steps file, but there are a few other details that could be moved to the steps file as well. So if the one above is Imperative does this modified version make it declarative?

Scenario: Allow me to change my password
  Given I am logged in as a SiteUser
  When I go to the "Change Password" page
    And I fill in my new password details
  Then my password details should be changed

At this stage I’m not sure, for now I will stay with the first style as it provides details that may be important to someone reading the feature but hides the non-essential detail in the steps file.

There is now a ActiveRecord adapter specifically for SQL Anywhere. It is available on RubyForge at sqlanywhere.rubyforge.org/. The source is hosted on GitHub and is available at github.com/sqlanywhere. This driver does not go through ODBC, but instead uses the new C API library to directly interface with SQL Anywhere databases. Please note that this driver can only be used with SQL Anywhere 10 and greater.

The solution I came up with was to monkey-patch the method responsible for checking the DB type to allow SybaseASA to be seen as a valid DB. I added the following code to my environment.rb:

# Monkeypatch the ODBC Adapter so that it will work with SybaseASA
# see http://odbc-rails.rubyforge.org/index.html
module ActiveRecord
  module ConnectionAdapters
    class ODBCAdapter < AbstractAdapter 
      alias :orig_dbmsNameToSym :dbmsNameToSym

      def dbmsNameToSym(dbmsName, dbmsVer)   
        begin
          # Call original method
          symbl = orig_dbmsNameToSym(dbmsName, dbmsVer)
        rescue ActiveRecord::ActiveRecordError
            # Catch exception if db not found in existing list, check
            # if SybaseASA, if not raise exception
            if dbmsName =~ /adaptiveserveranywhere/i
              symbl = :sqlanywhere
            else
              raise ActiveRecord::ActiveRecordError, "ODBCAdapter: Unsupported database (#{dbmsName})"
            end
        end
        return symbl
      end

    end
  end
end

So I needed to find an alternative that would work with SybaseASA or SQLAnywhere. After a lot of searching I came across a group dedicated to this task, at this stage there is not a lot of activity. One of the postings from Bryan Lahartinger proved very helpful, in the article he mentions "odbc-rails". I did a google search and found there is a Ruby project ODBC Adapter for Ruby on Rails / Active Record that has been developing an ODBC adapter for use with Rails.

The latest release has added support for SQLAnywhere so I dowloaded and installed it. There is a home page for this project which provides detailed installation instructions. I do my Rails development on Windows using InstantRails, a quick check confirmed that Christian Werner’s ODBC module comes preloaded with InstantRails so I did not have to install it separately. I downloaded the gem file for V2.0 from rubyforge and installed it using:

gem install -l activerecord-odbc-adapter-2.0.gem –include-dependencies

I setup my database.yml file to use the DSN I had previously defined to access the DB, i.e.

development:
  adapter: odbc
  dsn: mydatabase
  username: uid
  password: pwd

I started my server which loaded without any problem but when I tried to run my application I got the following error:

ODBCAdapter: Unsupported database (adaptiveserveranywhere)

As SybaseASA is the same as SQLAnywhere I changed the following line in odbc_adapter.rb (line #:1585) to get me going from:

elsif dbmsName =~ /SQLAnywhere/i or dbmsName =~ /adaptiveserveranywhere/i

So far everything seems to working without any problems, I’ve asked if it will be possible to get this change added to the gem, if not I will need to monkeypatch the source. Next I will attempt to do an install under Suse Linux as this is where the application will ultimately reside.

Update: I’ve now added the monkey-patch to my application see Rails ODBC Adapter with Sybase Adaptive Server Anywhere (SybaseASA)

One of my Rails projects require me to connect to a Sybase ASA database, I quickly figured out that I needed to install the sybase adapter as in Rails 2.0.2 these and some of the other databases have been pulled out of Rails core. According to the information in this article you can achieve this by using this command:

gem install activerecord-sybase-adapter

When I tried this I got the following error:

ERROR:  could not find activerecord-database-adapter locally or in a repository

The only way I got it to work was to use the -s option ("Use URL as the remote source for gems"), i.e.

gem install activerecord-sybase-adapter -s http://gems.rubyonrails.org

We are using rspec for our testing and when I went to write some tests to test some code that uses the refresh_to method I found out that the standard redirect_to rspec matcher does not work with refresh_to. The same problem exist for the standard test method assert_response :redirect and assert_redirected_to my_url, but the plugin does supply replacement tests for these methods. The problem is that it does not supply a replacement for the rspec matcher so I had to write my own. 

# The standard rspec redirect_to matcher does not work with the refresh_to
# plugin methods, i.e. refresh_to and refresh_back_or_default.
# This is also the case with the with the standard Rails functional
# tests - assert_response :redirect and assert_redirected_to my_url.
# The plugin has replacement test methods for these but they do not
# have an rspec replacement for redirect_to so I’ve had to write my own.
#
module Spec
  module Rails
    module Matchers
     
      class RefreshTo  #:nodoc:

        def initialize(controller, expected)
          @expected = expected
          @controller = controller
        end

        def matches?(response)
          match_data = response.body.match(/<meta http-equiv="refresh" content="0;url=([\S]+)">/)
          return false if (!match_data)
          parts = match_data[1].split("http://test.host")
          @actual = parts.last
          return match()
        end
         
        def match
          case @expected.class.to_s
            when ‘String’
              parts = @expected.split("http://test.host")                      
              @expected = parts.last
              return @actual == @expected
            when ‘Hash’
              @expected = @controller.url_for(@expected)
              return match()
          end         
        end

        def failure_message
          return %Q{expected redirect to #{@expected.inspect}, got redirect to #{@actual.inspect}}
        end

        def negative_failure_message
          return %Q{expected not to be redirected to #{@expected.inspect}, but was}
        end

        def description
          "redirect to #{@actual.inspect}"
        end
      end
     
      # :call-seq:
      #   response.should refresh_to(url)
      #   response.should refresh_to(:action => action_name)
      #   response.should refresh_to(:controller => controller_name, :action => action_name)
      #   response.should_not refresh_to(url)
      #   response.should_not refresh_to(:action => action_name)
      #   response.should_not refresh_to(:controller => controller_name, :action => action_name)
      #
      # Passes if the response is a redirect to the url, action or controller/action.
      # Useful in controller specs (integration or isolation mode).
      #
      # == Examples
      #
      #   response.should refresh_to("path/to/action")
      #   response.should refresh_to("http://test.host/path/to/action")
      #   response.should refresh_to(:action => ‘list’)
      def refresh_to(opts)
        RefreshTo.new(controller, opts)
      end
    end

  end
end 

Update 11 January 2008: SMERF web site completed.

I’m happy to announce the release of SMERF V0.0.1!

I’m still in the process of setting up the official web site but the source is now available for download. The README file contains a lot of information about the plugin including installation and configuration notes. You can also checkout the documentation in the rdoc directory which includes the API docs and the README in a more readable format.

There are several ways to download SMERF:

Direct download

Get it from RubyForge

Subversion

**Create a new smerf directory in your /vendor/plugins directory and change into the new directory

Check out the stable release

svn checkout http://smerf.rubyforge.org/svn/stable .

or Check out a particular release

svn checkout http://smerf.rubyforge.org/svn/tags/REL-0.0.1 .

or Check out the development code

svn checkout http://smerf.rubyforge.org/svn/trunk .

See the README for details of how to install and configure the plugin.

Until I get my bug tracker sorted out if you have any problems please feel free to contact me on smerf at cascadia dot com dot au.

Enjoy!

Update 11 January 2008: SMERF web site completed.

Update 9 January 2008: SMERF Released! 

Update 8 January 2008: I’ve completed the documentation and testing. I’ve created a project on RubyForge which is waiting approval. If this is not ready by tomorrow I will make an alternate link available for download, so if all goes well I should have a download available tomorrow.

I am putting the final touches to a new plugin called SMERF which stands for Simple MEta Rails Form. The plugin is a result of me extracting the code I used for one of my projects which I discussed in an earlier article Ruby on Rails Survey Builder.

I’ve spend the past few weeks rewriting parts of it to make it more generic so that it can be used for all sorts of things including survey’s, questionnaires, data collection forms and so on. Some of the important changes I’ve made include

• Allow question validations to be written using Ruby code. You can now create your own validation methods as required, there are also a couple of standard system validation methods that come with the plugin. You can specify any number of validation methods for a question by comma separating each method name, e.g. validation: validate_mandatory_question, validate_date_format
• User responses are now stored in a DB table allowing you to perform analysis on the question responses using SQL.

ToDo V0.2

• Currently there are no tests
• Allow forms to be broken into smaller forms, currently you get all questions on a single form
• Allow the save of user responses as you move from form to form

I’m currently writing a plugin generator that will make installation of the plugin easier, hopefully I’ll have this done very soon. I then need to finish the documentation which is mostly done.

I will keep you informed and let you know when the plugin will be available.