-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple output roots (e.g spec/javascript) would be awesome #7
Comments
I use guard-coffeescript for exactly that reason. This gives you also the possibility to have a headless BDD workflow, that would not be based on requests to Rails and thus impossible to implement with the Rack bases approach of Barista. Of course I still use Barista for the Rails integration. |
I have patched Jasmine gem ("rake jasmine" task) to use Barista to recompile all changed CoffeeScript files in app/coffeescripts and spec/coffeescripts before running tests - see https://groups.google.com/d/msg/jasmine-js/FcNpK1UkNiw/SeUkZi-pPlwJ Currently I needed to set directly output directory instance variable |
rsim i'm trying to use your script but rake jasmine fails with "no such file to load -- spec/javascripts/support/jasmine_config.rb" with ruby 1.9 |
jasmine gem has generated file spec/javascripts/support/jasmine_runner.rb which has lines jasmine_config_overrides = File.expand_path(File.join(File.dirname(__FILE__), 'jasmine_config.rb')) require jasmine_config_overrides if File.exists?(jasmine_config_overrides) Can you debug it and find out why spec/javascripts/support/jasmine_config.rb is not loaded by these lines? |
Hi rsim. I've got the same problem elcuervo does under Ruby 1.9 (works fine under Ruby 1.8). Apparently it doesn't have anything to do with those lines. Removing them or deleting every line in spec/javascripts/support/jasmine_runner.rb results in the same error. It seems to have nothing to do with your script either, but with the existence of that file
|
Apparently, line 34 in lib/jasmine/tasks/jasmine.rake should read: In order to work with Ruby 1.9. P.S: sorry for spamming this issue with questions about Jasmine. |
Ok, so we finally have proper support for per-framework output_roots - Simply use Barista.change_output_root! or the :output_root option on registering a framework. Cheers! |
I'd like to TDD my coffee script so it would be awesome if maybe frameworks could specify their own output directories so I can have one for jasmine that maps spec/coffeescripts to spec/javascripts. I'll take a look a forking and adding this and send a pull request if I get anywhere.
The text was updated successfully, but these errors were encountered: