Oliver Azevedo Barnes

I want to get autotest to run Steak acceptance tests whenever one of my rails app's relevant files is changed. After studying Rspec's and Cucumber's own autotest configs, I'm trying the following mappings:

Autotest.add_hook :initialize do |at|
  at.add_mapping(%r%^spec/acceptance/.*_spec.rb$%, true) { |filename, _|
    filename
  }

at.add_mapping(%r%^app/(models|controllers|helpers|lib)/.*rb$%) { 
    at.files_matching %r%^spec/acceptance/.*_spec.rb$%
  }

at.add_mapping(%r%^app/views/(.*)/.*rb$%) { 
    at.files_matching %r%^spec/acceptance/.*_spec.rb$%
  }
end

the first one works: whenever a Steak spec is changed, it gets run again.

but the second and third don't. changing any source files under the /app subdirectories just gets ignored.

what's the correct way to get these mappings to work?

thanks Oliver

How do I check the "Please fill out this field" message that appears above required fields when they're submitted empty?

Right now my cucumber scenario seems to ignore the empty field completely, submitting the form successfully.

(I'm validating the fields presence, and when submitting manually, the form does show the message)

We're using God to monitor our server processes, and were wondering if we should use something like Monit to make sure God gets up if something unexpected happens.

A quis custodiet ipsos custodes? conundrum :)

Googling for it didn't bring any mentions of this being done, which makes me think it's probably pretty rare.

Has anybody here seen a need for it?

Given

class Patient
  include Mongoid::Document
  embeds_many :notes
end

class Note
  include Mongoid::Document
  embedded_in :patient
end

class Diagnosis < Note
end

Is there a way to access a patient's diagnoses through a notes collection?

patient = Patient.new
patient.diagnoses << Diagnosis.new
patient.notes #=> #<Diagnosis...>

I managed to get this with non-embedded docs:

class Diagnosis < Note
  belongs_to :patient  
end

class Note
  include Mongoid::Document
end

class Patient
  include Mongoid::Document
  has_many :notes
  has_many :diagnoses
end

(Using STI here to later create Prescriptions and other types of notes and list them all together)

Looks like this version has been pulled from Rubygems, only beta.12 and beta.13 are listed:

http://rubygems.org/gems/sprockets

So you'd need to get the specific beta.2 branch from the repo, as Thariq suggests.

BUT, I'd probably go for one of the versions listed on rubygems - there must be good a reason why they were pulled ;)

I'm trying

client.update("testing annotations", {:annotations => [{'flag' => 'true'}].to_json})

which goes through, but when I fetch the resulting tweet using the client again, the Hashie object returned doesn't include the annotation anywhere.

what gives?

I'm using Twitter gem version 1.1.2, with rails 2.3

How do I stub an http request, like this one to the twitter api below, on a global scope so it's valid for all tests in a Test::Unit suite?

stub_request(:get, "https://api.twitter.com/1/users/show.json?screen_name=digiberber").
    with(:headers => {'Accept'=>'application/json', 'User-Agent'=>'Twitter Ruby Gem 1.1.2'}).
    to_return(:status => 200, :body => "", :headers => {})

This WebMock stub works within a TestCase subclass's setup() block, like

class MyTest < ActiveSupport::TestCase       
  setup do
    stub_request(...)...
  end
end

But doesn't get recognized if I put it within a global setup in TestCase itself:

require 'webmock/test_unit'
class ActiveSupport::TestCase  
  setup do
    stub_request(...)
  end
end

Which gives me the error:

NoMethodError: undefined method `stub_request' for ActiveSupport::TestCase:Class

I've also tried by patching the method def itself

def self.setup
  stub_request(...)
end

but it doesn't work either.

Something similar happens when I use FlexMock instead of WebMock. Seems to be a scope problem, but I can't figure out how to go around it. Ideas?

This post on different ways to setup() and teardown() led me to just do

class ActiveSupport::TestCase  
  def setup
    stub_request(...)
  end
end

hadn't thought of declaring it as an instance method. :P

When iterating results, you can store them in model objects, which in turn map to tables in sql databases (mysql, postgres, oracle), or documents in nosql dbs like mongodb.

Tweaking an example in the twitter gem's README:

# Find and store the 3 most recent marriage proposals to @justinbieber
Twitter::Search.new.containing("marry me").to("justinbieber").result_type("recent").per_page(3).each do |r|
  MyLocalTweetModel.create!(:from_user => r.from_user, :text => #{r.text}")
end

This can be done with any database, really.

The decision over which database to use depends on many other factors, such as where your app will be hosted, what traffic you expect, how you plan to scale it... and taste is definitely one of these factors, and not an unimportant one. I hate Active Record migrations, for instance, though I like its many other niceties. Active Record is the default ORM rails uses for sql databases.

If you're new to all this, just start on a simple sqlite database with Active Record. There's more of a learning-curve to the alternatives.

This discussion on the rails-i18n google group has an interesting solution:

#in a locale file
en: 
  education_levels: 
    gcses: Some GCSEs or less 
    collegeA: College A levels 
    some_university: Some University, no degree
    bachelors: University graduate - Bachelors or equivalent 
    masters: Masters degree
    professional: Professional Degree
    doctorate: Doctorate  

#And in a model: 
class Education < ActiveRecord::Base 
  def translated_education_level 
    I18n.t(education_level, :scope => :education_levels) 
  end 
end 

#In a helper: 
module EducationHelper 
  def education_levels 
    I18n.t(:education_levels).map { |key, value| [ value, key ] } 
  end 
end 

#And then in your view: 
<%= f.select :education_level, education_levels %>

In the comments to the solution for How do I find an image on a page with Cucumber/Capybara, somebody asked:

I can't seem to figure how to get this to work with URLs generated by Dragonfly. They look like this: /media/BAh_some_long_string_AwIw/12_11_52_810_5x5.jpg?s=7e360000, where 5x5.jpg is my file name. I've tried something like: //img[@src="/media//#{image}?s=*"] but it doesn't work. Got any tips? – Ramon Tayag Feb 25 at 4:18

I have a similar problem, only worse - in my case, the generated image paths don't even include a (jpg|png|gif) file name, they only have these really long ids:

<img src="/media/BAhbB1sHOgZmSSIdNGQ4MTEyOGU3ZjViZmQwZTQ4MDAwMDAyBjoGRVRbCDoGcDoKdGh1bWJJIg0yMDB4MjAwIwY7BlQ" />

(Using dragonfly with mongo/gridfs)

These paths get rendered alright, but I can't figure out how to find them in a Cucumber/Capybara step :P

Any ideas? I looked at the Dragonfly's features, but they only test the rendering of the image itself, without detecting it's existence within an html page.

Answering my own question, after talking to Dragonfly's author (he's working on making this easier):

#route
match '/media/:dragonfly/:file_name', :to => Dragonfly[:images]  

#model
class Store
  include MongoMapper::Document
  key :photo_uid, String
  key :photo_name, String
  image_accessor :photo
end

#view
<%= image_tag @store.photo.thumb('274x207#').url(:suffix => "/#{@store.photo_name}") if @store.photo %>

#cucumber
Then I should see the image "my_photo.png"

Then /^I should see the image "(.+)"$/ do |image|  
  page.should have_xpath("//img[contains(@src, \"#{image}\")]")
end

The key is adding an [attachment]_name field to the model, which Dragonfly populates automatically, and then passing it on as a suffix to url(). And the routes needs to allow for a :file_name param besides the generated dragonfly identifier.

Say I have a formtastic form that creates a Store and allows selection of Services it provides:

<%= semantic_form_for @store do |f| %>
  <%= f.inputs :services, :as => :check_boxes, :collection => Service.all %>
  <%= f.buttons %>
<% end -%>

I want to allow the user to add a new Service in case he doesn't see it in the options, right from the form.

There are many examples for simple nested form element addition, say of a Task entry to a Project, and even a gem that helps with this, but I haven't found any that create a new resource so it'll show as part os checkbox or select options.

Got it working this way:

<%= semantic_form_for @store do |f| %>
  <%= f.inputs :services, :as => :check_boxes, 
                          :collection => Service.all,
                          :wrapper_html => { :id => 'service_fields' } %>  
  <%= f.buttons %>
<% end -%>

Added an id to the parent list item around the checkbox field listing, so it can be accessed by this js after submitting a text field with the new service name:

<input type="text" id="new_service_name" />
<input type="button" value="ok" id="btnSave" />                                

<script type="text/javascript">        
  $(document).ready(function() {
    $('#btnSave').click(function() {
      $.ajax({
        url: '/admin/services.json',
        type: 'POST',
        dataType: 'json',
        data: 'service[name]=' + $('#new_service_name').val(),
          success: function(data) {
            addCheckbox(data);
          }
        });
      });
    });

    function addCheckbox(name) {
      var container = $('#service_fields fieldset ol');
      var inputs = container.find('input');
      var id = inputs.length+1;

      //var html = '<input type="checkbox" id="cb'+id+'" value="'+name+'" /> <label for="cb'+id+'">'+name+'</label>';
      var html = '<li><label for="store_services_'+id+'"><input id="store_services_'+id+'" name="store[services][]" type="checkbox" value="'+id+'" />'+name+'</label></li>';
      container.append($(html));
    }
</script>

Then, in ServicesController:

class ServicesController < ApplicationController  
  respond_to :json

  def create
    service = Service.create!(params[:service])    
    respond_with(service)
  end
end

The following formtastic form checkbox field set:

<%= semantic_form_for @store do |f| %>
  <%= f.inputs do %>
    <%= f.input :services, :as => :check_boxes, :collection => Service.all %>  
  <% end -%>
<% end -%>

is sending bad params for :services on a Cucumber test using Capybara, making the test fail, while the actual app sends the correct ones, which gets processed fine:

#cucumber steps using the boiler_plate capybara web_steps.rb:
Given a "Mail Order" service
...(steps for rest of the form)...
When I check "Mail Order" 
And I press "Create Store"
Then I should see "Store was successfully created."
And I should see "Mail Order"

#params sent by cucumber
"store"=>{"services"=>["[\"4d8247ed7f5bfd2275000004\"]"]

#params sent by app on manual test
"store"=>{"services"=>["4d8247ed7f5bfd2275000004"]}

Though the html form itself is rendered the same way in both cases:

<input id="store_services_4d8247ed7f5bfd2275000004" name="store[services][]" type="checkbox" value="4d8247ed7f5bfd2275000004" />

Seems like somewhere during the request params-building, the form key/value pairs for that field get parsed differently when submitted by Cucumber/Capybara.

Anyone else come across this?

Answering my own question:

Got a pointer from Capybara's author, Jonas Nicklas, that led me to this rack-test patch which hasn't been committed yet

For now I'm just using the fork and branch where the patch lives:

gem 'rack-test', :git => 'https://github.com/econsultancy/rack-test.git', :branch => 'econsultancy-20110119'

And that does the trick. I imagine this patch will be merged in very soon though, as it was submitted a couple of months ago.

I need to make a site's menu navigate like OSX's Finder in column view, where each level appears next to its parent in a vertical column.

Have been googling this for a couple of hours now, and this Jquery plugin seems to be the closest match (There's a demo here)

From a first trial, it seems somewhat hard to customize. I need it to behave and look differently in a couple of ways:

• no scrolls, neither vertical nor horizontal. it needs to act more like a web menu than like a select box
• when clicking on the final link, after navigating the subs, the whole page should be redirected to the url, and the menu should keep the state.
• the final link should be clickable right away, like on the demo. on my trial, it loads yet another column with a duplicate of the link, which in turn is clickable.

Does anybody know how to accomplish these with this plugin, or could point me towards simpler implementations that are closer to these specs?

Here's the menu html structure:

<ul id="nav">
    <li class="current" id="nav-o-que-estamos-fazendo">
        <a href="/o-que-estamos-fazendo/">O que estamos fazendo</a>
        <ul id="nav-o-que-estamos-fazendo-children">
            <li id="nav-o-que-estamos-fazendo-children-ficcao">
                <a href="/o-que-estamos-fazendo/ficcao/">Ficção</a>
            </li>
            <li class="current" id="nav-o-que-estamos-fazendo-children-documentario">
                <a href="/o-que-estamos-fazendo/documentario/">Documentário</a>
                <ul id="nav-o-que-estamos-fazendo-children-documentario-children">
                    <li class="current" id="nav-o-que-estamos-fazendo-children-documentario-children-josephine-king">
                        <a href="/o-que-estamos-fazendo/documentario/josephine-king/">Josephine King</a>
                    </li>
                </ul>
            </li>
            <li id="nav-o-que-estamos-fazendo-children-televiso">
                <a href="/o-que-estamos-fazendo/televiso/">Televisão</a>
            </li>
            <li id="nav-o-que-estamos-fazendo-children-museus">
                <a href="/o-que-estamos-fazendo/museus/">Museus</a>
            </li>
        </ul>
    </li>
    <li id="nav-o-que-ja-fizemos">
        <a href="/o-que-ja-fizemos/">O que já fizemos</a>
    </li>
    <li id="nav-o-que-somos">
        <a href="/o-que-somos/">O que somos</a>
    </li>
    <li id="nav-quem-somos-contato">
        <a href="/quem-somos-contato/">Quem somos | contato</a>
    </li>
    <li id="nav-mirabolancias">
        <a href="/mirabolancias/">Mirabolâncias</a>
    </li>
</ul>

As generated by the 'nav' liquid tag on Harmonyapp)

With the following Store and Service models, managed with MongoMapper:

class Store
  include MongoMapper::Document         
  key :service_ids, Array, :typecast => 'ObjectId'
  many :services, :in => :service_ids
end

class Service
  include MongoMapper::Document         
  key :name, String  
  many :stores, :foreign_key => :service_ids  
end

I have this form, done with Formtastic:

<%= semantic_form_for @store, :url => admin_store_path(@store), :method => :put do |form| %>
  <%= form.input :service_ids, :label => "Select Store Services", 
                               :as => :check_boxes, 
                               :collection => Service.all %>
<% end -%>

The controller uses Inherited Resources, and the edit action is implicit.

When editing a @store with services already associated with it, the checkboxes for the latter don't show as checked.

Formtastic's README warns it doesn't support MongoMapper officially, but it also says people have been using both together successfully, and I've seen some examples of this online.

I suspect Inherited Resources also doesn't support it, from what I've seen from Devise + Simple Form, both from the same authors and which don't support MM. They're working towards using an ORM adapter in their gems, but it isn't ready yet AFAIK.

And I've had problems with it already, I'm overriding the update action to get it to work:

  def update
    store = Store.find(params[:id])    
    if store.update_attributes!(params[:store])

      flash[:notice] = 'Store was successfully updated.'
      redirect_to admin_store_path(store)
    else
      redirect_to new_store_path
    end
  end  

Does anybody know where the conflict with MM is, either in Formtastic or IR, and a hack just to get these checkboxes checking?

From reading the db:test tasks's source, it looks like they only care about grabbing the test db info from database.yml, but don't care which actual environment they're doing it under.

You might need to run rake db:test:prepare RAILS_ENV=test to ensure you're under the test environment.

One way might be to dump the dev data to yaml (this plugin does that and there are probably others that will do the trick), and then use db/seeds.rb to write a script loading its contents and using rails models to recreate them on the production db with rake db:seed

rake db:seed won't hose your data (it just loads db/seeds.rb, see the source here and here), but be sure to backup your data before anything :)

I'd suggest playing with a sandbox app and db clone before going ahead and running this on production.

Try

ActiveResource::Base.include_root_in_json = false

If you need to keep the top root and just remove the associated credit card object's root, then you might need to customize the json output with #to_json, like this:

def to_json(options = {})
  { "user"=>
      {"credit_card"=>
        {"number"=> self.credit_card.number }
       }, 
        "user_name"=> self.user_name
   }.to_json(options)
end

From that picture, I'm understanding you just want to exclude them from the coverage analysis?

If so, something like this might help:

http://psixty.wordpress.com/2010/06/22/how-to-exclude-files-in-rcova-code-coverage-tool-in-ruby/

One way would be to avoid hitting the API at all, by faking the responses with Fakeweb

This will speed up your tests :) And decoupling them from external services is a Good Thing in general - saves bandwidth, ensures your tests will run if the service is down, etc

snapshot is set as a local variable in controller, so the template doesn't see it. Set it as an instance variable:

@snapshot = Snapshot.find(params[:id])

then in the template:

:locals   => {:snapshot => @snapshot

Are there any implementations (open source or proprietary) of TinyMCE-like widgets for iOS apps?

If not, are there any references, tutorials, recipes etc no how to roll one's own?

Just came out of a project running Rails 2.3.* and Ruby 1.9.*, and had quite a few versioning issues like this, with test-unit and other libs.

If that stack isn't a project requirement, I'd just upgrade to the latest stack: Rails 3.0.5 and Ruby 1.9.2. It'll make your life a hell of a lot easier.

You'll be able to use Rspec 2 with it, along with all the new Rails 3 goodies. And you'll skip having to come up to speed with all of this later ;)

Try

<% if f.object.is_white == true %>

Seem to remember you could access the object this way (not 100% sure though ;)

You'll need to refactor your url helpers to include the admin namespace. In the error's case, it'd be

<td><%= link_to 'Show', admin_kategori_path(kategori) %></td>

Same goes for the redirects in the controller

#in AdminController#create
redirect_to(admin_kategori_path(@kategori))

To see all the generated route helpers, from the console do

rake routes