Closed ep-wac closed 11 years ago
Hi,
I don't get the issue. Please share your Gemfile.lock
or tell us what's your Guard, guard-minitest and Minitest versions.
Hi @rymai nice of you to comment on my quails. It's either a change of convention which I've missed - or some setting, I've managed to garble (blush)
I liked the kind of testing where all tests where performed and reporting with a single line ( pass | fail | error ) but then one day I hit a particular troublesome test and being the lazy bugger, I somehow managed to scrape together a setup which would let me drop to a prompt using binding.pry
That however had me pushed sideways with this issue - showing the prompt on every fail and error.
I've edited/shared - and my versions are like this:
Appreciating your time and interest!
$ bundle list
Gems included by the bundle:
* actionmailer (3.2.8)
* actionpack (3.2.8)
* activemodel (3.2.8)
* activerecord (3.2.8)
* activeresource (3.2.8)
* activesupport (3.2.8)
* ancestry (1.3.0)
* ansi (1.4.3)
* arel (3.0.2)
* awesome_print (1.1.0)
* backports (3.3.0)
* bcrypt-ruby (3.0.1)
* better_errors (0.8.0)
* binding_of_caller (0.7.1 3fe0125)
* browser_details (0.0.4)
* builder (3.0.4)
* bullet (4.6.0)
* bundler (1.3.5)
* capybara (2.1.0)
* carrierwave (0.8.0)
* carrierwave_backgrounder (0.2.1)
* childprocess (0.3.9)
* choice (0.1.6)
* chosen-rails (0.9.13)
* chronic (0.9.1)
* clear_eyes (0.1.6)
* code_analyzer (0.3.1)
* coderay (1.0.9)
* coffee-filter (0.1.3)
* coffee-rails (3.2.2)
* coffee-script (2.2.0)
* coffee-script-source (1.6.2)
* colored (1.2)
* commonjs (0.2.6)
* daemons (1.1.9)
* database_cleaner (0.9.1)
* debug_inspector (0.0.2)
* delayed_job (3.0.5)
* delayed_job_active_record (0.4.4)
* devise (2.2.3)
* erubis (2.7.0)
* eventmachine (1.0.3)
* execjs (1.4.0)
* factory_girl (4.2.0)
* factory_girl_rails (4.2.1)
* faye-websocket (0.4.7)
* ffi (1.8.1)
* formatador (0.2.4)
* friendly_id (4.0.9)
* geokit (1.6.5)
* geokit-rails3 (0.1.5)
* guard (1.8.0)
* guard-spork (1.5.0)
* guard-sporkminitest (0.0.2)
* haml (3.1.8)
* has_scope (0.5.1)
* hike (1.2.2)
* hirb (0.7.1)
* home_run (1.0.9)
* http_parser.rb (0.5.3)
* i18n (0.6.4)
* inherited_resources (1.4.0)
* interactive_editor (0.0.10)
* interception (0.3)
* journey (1.0.4)
* jquery-rails (2.2.1)
* jquery-ui-rails (4.0.2)
* json (1.7.7)
* kaminari (0.14.1)
* less (2.3.2)
* less-rails (2.3.3)
* libv8 (3.11.8.17)
* liquid (2.5.0)
* liquify (0.2.7)
* listen (1.1.5)
* lumberjack (1.0.3)
* mail (2.4.4)
* meta-tags (1.4.1)
* meta_request (0.2.1)
* method_source (0.8.1)
* mime-types (1.17.2)
* mini_magick (3.5.0)
* minitest (4.7.3)
* minitest-capybara (0.1.0)
* minitest-matchers (1.3.0)
* minitest-metadata (0.4.0)
* minitest-rails (0.9.2)
* minitest-rails-capybara (0.9.0)
* minitest-spec-rails (4.7.3)
* money (5.1.1 5030b58)
* money-rails (0.8.1)
* multi_json (1.7.2)
* mustache (0.99.4)
* mysql2 (0.3.11)
* nested_form (0.3.2 a25eebe)
* net-dns (0.7.1)
* nokogiri (1.5.9)
* nordea (1.1.0 f722985)
* open4 (1.3.0)
* orm_adapter (0.4.0)
* paper_trail (2.7.1)
* poltergeist (1.2.0)
* polyamorous (0.5.0)
* polyglot (0.3.3)
* pry (0.9.12.2)
* pry-exception_explorer (0.2.3)
* pry-nav (0.2.3)
* pry-rails (0.2.2)
* pry-rescue (1.1.1)
* pry-stack_explorer (0.4.9)
* rack (1.4.5)
* rack-cache (1.2)
* rack-contrib (1.1.0)
* rack-protection (1.5.0)
* rack-recaptcha (0.6.6)
* rack-ssl (1.3.3)
* rack-test (0.6.2)
* rails (3.2.8)
* rails-erd (1.1.0)
* rails_best_practices (1.13.4)
* railties (3.2.8)
* rake (10.0.4)
* rake-remote_task (2.2.1)
* ransack (0.7.2)
* rb-fsevent (0.9.3)
* rb-inotify (0.9.0)
* rb-kqueue (0.2.0)
* rb-readline (0.4.2)
* rdiscount (2.0.7.2)
* rdoc (3.12.2)
* ref (1.0.4)
* responders (0.9.3)
* rmagick (2.13.2)
* routing_concerns (0.1.0)
* ruby-graphviz (1.0.9)
* ruby-progressbar (1.0.2)
* sass (3.1.21)
* sass-rails (3.2.6)
* sexp_processor (4.2.1)
* simple_enum (1.6.4)
* sinatra (1.3.6)
* sinatra-contrib (1.3.2)
* sinatra-reloader (1.0)
* slim (1.3.8)
* slop (3.4.5)
* smt_rails (0.2.6 acb857a)
* spoon (0.0.3)
* spork (0.9.2)
* spork-minitest (0.0.3)
* sprockets (2.1.3)
* squeel (1.0.18)
* subexec (0.2.3)
* temple (0.6.4)
* terminal-notifier-guard (1.5.3)
* themes_for_rails (0.5.1)
* therubyracer (0.11.4)
* thin (1.5.1)
* thor (0.18.1)
* tilt (1.3.7)
* timeliness (0.3.7)
* treetop (1.4.12)
* tries (0.2.1)
* turbo-sprockets-rails3 (0.2.13)
* turn (0.9.6)
* twitter-bootstrap-rails (2.2.6)
* tzinfo (0.3.37)
* uglifier (2.0.1)
* uniform_notifier (1.2.0)
* useragent (0.6.0)
* validates_timeliness (3.0.14)
* vlad (2.4.1)
* vlad-git (2.2.0)
* warden (1.2.1)
* whenever (0.8.2)
* xpath (2.0.0)
* yajl-ruby (1.1.0)
Thanks for the gems list, however it looks like you're not even using guard-minitest
(you're using guard-sporkminitest
)!
Also, regarding that:
I somehow managed to scrape together a setup which would let me drop to a prompt using binding.pry
What did you change exactly (in which file etc...)?
that is so true - sorry! I'll go bark up some other tree :)
I added the pry* family of gems and in so far as I remember, that was when I started seeing the prompt 'all over' - even when tests were "just" failing
I'm so sorry to have waisted your bandwidth on this issue - it clearly must belong somewhere else!
cheers E
realize this is closed - but the prompt gave it away ;)
that particular prompt is a result of using Turn and it's c.format = :cue
configuration option. You probably forgot all about it but it sits right there in your test/test_helper.rb ;)
@wdiechmann that was the best news in this week - huzzah - now I have my test 'monitor' back to what it used to be. I have to stop adding stuff I haven't got a clue about in the first place (blush)
thank you so much!
On Sat, Jun 15, 2013 at 5:06 PM, wdiechmann notifications@github.comwrote:
realize this is closed - but the prompt gave it away ;)
that particular prompt is a result of using Turnhttps://github.com/TwP/turnand it's c.format = :cue configuration option. You probably forgot all about it but it sits right there in your test/test_helper.rb ;)
— Reply to this email directly or view it on GitHubhttps://github.com/guard/guard-minitest/issues/63#issuecomment-19497831 .
I've used guard for quite some time now and only recently I've all of a sudden start getting put at the Guard prompt? The output is like this:
I really could do without the
[c,i,q,r,t,#,?]
prompt kind of thing - but I'll be darn if I can find the setting, how to disable it :(If I could have one push me in the right direction, I'd really appreciate it
cheers E
My Guardfile has the standard stuff and a few env initializations - like
and finally my Gemfile.lock holds