> > On 10/4/07, Nathan Sutton < [EMAIL PROTECTED]> wrote:
> > > How would I go about writing specs for a lib, particularly one with
> > > all protected and private methods. I'm trying to spec the
> > > AuthenticatedSystem library from the rails restful_authentication
> > > plugin:
> > > http://pas
AuthenticatedSystem library has tests already written for it.
Just as Jim said you needn't write specs for it.
But if you did want to write spec's for the AuthenticatedSystem then you'd
create a directory inside the plugin directory with all the other directory
and files pointing the paths to the
Since it's a plugin, then I would not spec it, and spec the files that use
it instead.
Jim Deville
On 10/4/07, Nathan Sutton <[EMAIL PROTECTED]> wrote:
>
> How would I go about writing specs for a lib, particularly one with
> all protected and private methods. I'm trying to spec the
> Authentica
On Oct 4, 2007, at 6:24 AM, David Chelimsky wrote:
> On 10/4/07, Nathan Sutton <[EMAIL PROTECTED]> wrote:
>> How would I go about writing specs for a lib, particularly one with
>> all protected and private methods. I'm trying to spec the
>> AuthenticatedSystem library from the rails restful_authe
On 10/4/07, Nathan Sutton <[EMAIL PROTECTED]> wrote:
> How would I go about writing specs for a lib, particularly one with
> all protected and private methods. I'm trying to spec the
> AuthenticatedSystem library from the rails restful_authentication
> plugin:
> http://pastie.caboo.se/103625
I th
How would I go about writing specs for a lib, particularly one with
all protected and private methods. I'm trying to spec the
AuthenticatedSystem library from the rails restful_authentication
plugin:
http://pastie.caboo.se/103625
Also, when you're mocking objects, a side-effect is helping y
