hi there,
I’ve been spec-ing classes in my lib/ directory, but until now only get
spec
to run using:
script/spec spec/lib/
is there a way to make autotest load specs for this directory too?
thanks in advance,
joaquin
On Thu, Sep 18, 2008 at 6:54 AM, Joaquin Rivera P.
[email protected]wrote:
I’ve been spec-ing classes in my lib/ directory, but until now only get
spec to run using:script/spec spec/lib/
is there a way to make autotest load specs for this directory too?
I know this isn’t much help, but on my system autotest runs lib specs.
However, I did just start my VimMate project by making rails.vim’s
‘alternate file’ handling respect lib files and lib spec files.
///ark
hey Mark you’re right,
all of a sudden I notice that specs in lib/spec do really get runned by
autotest…
I’ll try to repeat the case in another project, I guess maybe only after
autotest reruns all the specs (it does so from time to time) is that
new
directories inside spec/ get runned, or maybe I just overlooked last
time
(sorry is that results to be case), we’ll see
thanks,
joaquin
oopps, here:
all of a sudden I notice that specs in* lib/spec* do really get runned
by
autotest…
i meant:
all of a sudden I notice that specs in spec/lib do really get runned
by
autotest…
thx
joaquin
2008/9/18 Joaquin Rivera P. [email protected]
On Thu, Sep 18, 2008 at 9:17 AM, Joaquin Rivera P.
[email protected]wrote:
I’ll try to repeat the case in another project, I guess maybe only after
autotest reruns all the specs (it does so from time to time) is that new
directories inside spec/ get runned, or maybe I just overlooked last time
(sorry is that results to be case), we’ll see
In general, if you add any spec files, you must restart autotest. Even
Ctrl-C to run all tests does not refresh its list of targets in my
experience.
///ark
On Sep 18, 2008, at 12:27 PM, “Mark W.” [email protected] wrote:
my experience.
Is anybody having a different experience with T::U?