You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2009/03/18 17:11:50 UTC
[jira] Commented: (BUILDR-269) rspec bdd is broken
[ https://issues.apache.org/jira/browse/BUILDR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683055#action_12683055 ]
Assaf Arkin commented on BUILDR-269:
------------------------------------
any idea how to spec/test this, so it doesn't break again?
> rspec bdd is broken
> -------------------
>
> Key: BUILDR-269
> URL: https://issues.apache.org/jira/browse/BUILDR-269
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Reporter: Jeff Hodges
> Fix For: 1.3.4
>
> Attachments: 0001-Kernel.gem-is-a-private-method-on-Kernel-and-it-cann.patch, 0002-mkdir_p-does-not-exist-except-on-FileUtils-and-dump_.patch, 0003-adding-a-join-n-on-to-the-returned-backtrace-to.patch
>
>
> There a multitude of bugs in the running of rspec in buildr in the current github repository.
> These patches fix the issues with:
> * mkdir_p being called without being called on FileUtils
> * a call is made to Error.dump_yaml with only one argument instead of two
> * Kernel.gem is a private method, and this patch changes the calls to it into Kernel#send calls that gets around it
> * for yucks, I made the backtrace that come back on errors nicer by turning it into a pretty string. (we should probably not have this stack trace and the usual rspec --trace one being returned at the same time like it does now. it's pretty confusing.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.