I got spec_server working today, and was literally ecstatic about the speed of response from running a spec. Yelps and all-sorts, very un- British, I can tell you ;) However I''m starting to notice that it doesn''t seem to be picking up changes. I''m working on a helper function at the moment, and I get a different (old) test failure from spec -X as I do from straight up, slow old spec. rspec 1.1.12 rails 2.2 Any advice? Matt Wynne http://blog.mattwynne.net http://www.songkick.com
On Wed, Jan 14, 2009 at 12:05 PM, Matt Wynne <matt at mattwynne.net> wrote:> I got spec_server working today, and was literally ecstatic about the speed > of response from running a spec. Yelps and all-sorts, very un-British, I can > tell you ;) > > However I''m starting to notice that it doesn''t seem to be picking up > changes. I''m working on a helper function at the moment, and I get a > different (old) test failure from spec -X as I do from straight up, slow old > spec. > >Make sure you have config.cache_classes = false in test.rb.. ///ark -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090114/597d3f55/attachment.html>
On 14 Jan 2009, at 20:17, Mark Wilden wrote:> On Wed, Jan 14, 2009 at 12:05 PM, Matt Wynne <matt at mattwynne.net> > wrote: > I got spec_server working today, and was literally ecstatic about > the speed of response from running a spec. Yelps and all-sorts, very > un-British, I can tell you ;) > > However I''m starting to notice that it doesn''t seem to be picking up > changes. I''m working on a helper function at the moment, and I get a > different (old) test failure from spec -X as I do from straight up, > slow old spec. > > > Make sure you have > > config.cache_classes = false > > in test.rb..Yes! ... but it appears to totally bork the features, at least on our build server. Anyone else had this problem, and got a workaround? I''m actually running the features in a separate environment (''features'') locally, but I haven''t got around to persuading the build server to do that yet. Matt Wynne http://blog.mattwynne.net http://www.songkick.com
On Jan 14, 2009, at 3:05 PM, Matt Wynne wrote:> I got spec_server working today, and was literally ecstatic about > the speed of response from running a spec. Yelps and all-sorts, very > un-British, I can tell you ;) > > However I''m starting to notice that it doesn''t seem to be picking up > changes. I''m working on a helper function at the moment, and I get a > different (old) test failure from spec -X as I do from straight up, > slow old spec. > > rspec 1.1.12 > rails 2.2 > > Any advice?I''ve also found shared example groups to be quite buggy (not reloading) Scott
On Jan 14, 2009, at 6:10 PM, Matt Wynne wrote:> > On 14 Jan 2009, at 20:17, Mark Wilden wrote: > >> On Wed, Jan 14, 2009 at 12:05 PM, Matt Wynne <matt at mattwynne.net> >> wrote: >> I got spec_server working today, and was literally ecstatic about >> the speed of response from running a spec. Yelps and all-sorts, >> very un-British, I can tell you ;) >> >> However I''m starting to notice that it doesn''t seem to be picking >> up changes. I''m working on a helper function at the moment, and I >> get a different (old) test failure from spec -X as I do from >> straight up, slow old spec. >> >> >> Make sure you have >> >> config.cache_classes = false >> >> in test.rb.. > > Yes! > > ... but it appears to totally bork the features, at least on our > build server. Anyone else had this problem, and got a workaround?Don''t version control config/environments/test.rb. Keep around config/ environments/test.rb.example, and copy it to test.rb after check out. Scott