Question

I’m building out a medium-sized application using Sinatra and all was well when I had a single app.rb file and I followed Aslak’s guidance up on Github:

https://github.com/cucumber/cucumber/wiki/Sinatra

As the app grew a bit larger and the app.rb file started to bulge, I refactored out a lot of of the bits into “middleware” style modules using Sinatra::Base, mapping things using a rack-up file (config.ru) etc.

The app works nicely – but my specs blew up as there was no more app.rb file for webrat to run against (as defined in the link above).

I’ve tried to find examples on how to work this – and I think I’m just not used to the internal guts of Cuke just yet as I can’t find a single way to have it cover all the apps. I tried just pointing to “config.ru” instead of app.rb – but that doesn’t work.

What I ended up doing – which is completely hackish – is to have a separate app.rb file in my support directory, which has all the requires stuff so I can at least test the model stuff. I can also specify routes in there – but that’s not at all what I want to do.

So – the question is: how can I get Cucumber to properly work with the modular app approach?

Answer 1

Update to include dealing with multiple Sinatra apps

Require the file where your app comes together and change

  def app
    Sinatra::Application
  end

to

 def app
    Rack::Builder.new do
      map '/a' { run MyAppA }
      map '/b' { run MyAppB }
    end
  end

and just test the app proper.

eg, if you define middleware in your config.ru that you want to test, maybe move loading those into your app’s definition.