BTW, I didn't thank you for your response, Jon. I appreciate you sharing
your expertise.
On Monday, July 29, 2019 at 5:15:47 PM UTC-7, Jack R-G wrote:
>
> Easier said than done, I think. Are you suggesting that I focus on
> minimizing my existing project, or are you suggesting that I focus on
> trying to get autotest working with a new, dummy project with minimal code?
>
> Also, do you have a solution that you like for CI on a personal
> development system - autotest was so simple to use (when I started using
> it), and I can't imagine doing the work to setup up one of the bigger
> commercial CI solutions like Jenkins or Travis.
>
> I got further (maybe) by removing some of the gem references from my
> Gemfile (autoest-fsevent, autotest-growl) and replacing them with just
> "autotest". I then did "bundle install". When I now run autotest, I get the
> following:
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/ruby -I.:lib:test -e "gem
> 'minitest'; %w[minitest/autorun test/performance/browsing_test.rb
> test/test_helper.rb test/unit/test_webhooks.rb].each { |f| require f }" --
> --server 70284
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:22:in
>
> `remove_method': method `run' not defined in Minitest::Unit::TestCase
> (NameError)
>
> from
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:22:in
>
> `<class:TestCase>'
>
> from
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:17:in
>
> `<class:Unit>'
>
> from
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:16:in
>
> `<module:MiniTest>'
> and
>
> Unhandled exception: undefined method `results' for
> #<Autotest:0x007f9b4b06fa20>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/result.rb:7:in
>
> `initialize'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/growl.rb:138:in
>
> `new'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/growl.rb:138:in
>
> `block in <module:Growl>'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in
>
> `[]'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in
>
> `block in hook'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in
>
> `each'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in
>
> `any?'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in
>
> `hook'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:314:in
>
> `run_tests'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:292:in
>
> `get_to_green'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:263:in
>
> `block in run'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:261:in
>
> `loop'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:261:in
>
> `run'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:152:in
>
> `run'
>
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/bin/autotest:5:in
>
> `<top (required)>'
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/autotest:25:in `load'
>
> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/autotest:25:in `<main>'
>
> Any thoughts about these errors?
>
> On Monday, July 29, 2019 at 8:02:10 AM UTC-7, Jon Rowe wrote:
>>
>> Honestly I’d start by stripping it back to a minimal implementation, you
>> shouldn’t need growl for it to work, you could also consider finding a
>> replacement test watcher, I know Guard came after auto test, but I’m not
>> sure if theres anything newer!
>>
>> Jon Rowe
>> ---------------------------
>> ma...@jonrowe.co.uk
>> jonrowe.co.uk
>>
>> On 28 July 2019 at 01:36, Jack R-G wrote:
>>
>> I started a project about 8 years ago and was using RSpec and autotest.
>> For reasons not important to this discussion, I stopped using both of them
>> after a year or two. Now I want to resume using them and am having problems
>> getting them working again. RSpec is working just fine (that is, when I run
>> it it runs my tests), but I can't get autotest to work. I've done a few
>> things to try to get it to work, but currently when I type "autotest" I get
>>
>> loading autotest/rails_rspec2
>>
>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:128:in
>>
>> `require': cannot load such file -- autotest/growl (LoadError)
>>
>> I've done a "bundle install" and "bundle update", so I believe I have the
>> "best" versions that I can have.
>>
>> My Gemfile looks like:
>> ...
>> gem 'ZenTest'
>> gem 'shoulda-matchers'
>> gem 'webrat', '0.7.1'
>> gem 'factory_girl_rails'
>> gem 'autotest-growl'
>> gem 'autotest-fsevent'
>> ...
>>
>> Gemfile.lock shows that I've got
>> ZenTest (4.11.2)
>> autotest-fsevent (0.2.14)
>> autotest-growl (0.2.16)
>>
>> With all that seems to have happened since then (ZenTest separating out
>> growl, OS X no longer requiring growl, etc.) I'm really kinda lost as to
>> where my system should be.
>>
>> Oh, and I should have said earlier: Ruby 2.0, Rails 3.2 (the reason I'm
>> trying to re-integrate RSpec is that I now need to migrate to newer
>> versions of Ruby and Rails). I can't even really figure out where to go for
>> help with this, so if someone knows a better forum than here for the
>> question, please let me know.
>>
>> Thanks!
>>
>>
--
You received this message because you are subscribed to the Google Groups
"rspec" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rspec+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rspec/9080491f-342f-48f5-809d-165cc407fc71%40googlegroups.com.
