Explaining the cucumber module

This post is a little bit of explaining for the cucumber testing module I wrote earlier this month. This module is absolutely necessary in order to make cucumber testing possible for Drupal. The reason for this is that it does two things:

1. Creation of the test users

This module creates for each and every role it finds in your drupal instance. Let's say you have 4 roles: Administrator, Authenticated User, Editor and Picture Editor. It will create the following users/passwords

user: cucumber_[role_name_with_underscores]
password: cucumber_[role_name_with_underscores]

Those users will have the respective roles assigned.

2. Enable testing in overlays

Cucumber and the drupal overlays don't play along very well. In cucumber, there's a method defined as followed:

within_frame "my-frame" do
  fill_in 'edit-title', :with => "This is a test title"
  click_button 'edit-submit'
end

There are two iframe elements that toggle each time a link is clicked for better responsiveness. This is why both of the iframes don't get an ID attribute. This module replaces the current javascript file with an adapted version of it. Now, the active iframe will be assigned the id overlay-active.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.