Error Loading Autotest Style
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up “autotest/rails […] doesn't […] exist. Aborting” up vote 11 down vote favorite 5 I'm finding that autotest has stopped working... $ autotest loading autotest/rails Autotest style autotest/rails doesn't seem to exist. Aborting. According to this blog post, the common reason for this error is that people don't have the autotest-rails gem installed. However, I definitely have that installed: autotest-rails (4.1.0) ZenTest (4.1.4, 4.1.3, 4.1.1, 4.0.0, 3.11.1, 3.11.0, 3.10.0, 3.9.3, 3.9.2) I haven't installed any new gems today or yesterday, though I might have done a gem update yesterday. Another issue I saw mentioned was incompatibility with Ruby 1.9, but I'm using MRI Ruby 1.8.6. ruby-on-rails ruby testing tdd zentest share|improve this question edited Aug 20 '09 at 2:24 asked Aug 20 '09 at 0:00 Ethan 19.4k50150220 add a comment| 7 Answers 7 active oldest votes up vote 17 down vote I just hit this problem today. My versions were: autotest-rails (4.1.0) ZenTest (4.1.4, 3.10.0) I did a 'sudo gem cleanup ZenTest' and autotest now runs. Hope this helps. :-) share|improve this answer answered Sep 15 '09 at 5:45 Adam 1712 Worked for me as well. –nertzy Sep 25 '09 at 15:15 Thanks. Tried that but it didn't work. –Ethan Oct 15 '09 at 20:41 This also worked for me, thanks! –banderson623 Mar 12 '10 at 14:05 Thanks it worked for me as well. –Thi Jun 2 '11 at 21:29 add a comment| up vote 2 down vote accepted Downgraded ZenTest from 4.1.4 to 4.1.3 and autotest works again. share|improve this answer answered Aug 20 '09 at 2:25 Ethan 19.4k50150220 add a comment| up vote 2 down vote I just upgraded to ZenTest 4.1.4 with autospec and my big app is working just fine. (I had to do a script/generate rspec) I also created a dummy test app with rails and a dummy scaffold and confirmed autotest is working just fine. There must be something going on with your config. Did you do a full sudo gem update ? share|improve this answer answered Aug 20 '09 at 4:39 Sam Saffron 74.3k55259446 Yes, I sure did. That's puzzli
In Problems running RSpec 2 with autotest/autospec Kristian Mandrup (kmandrup) on 2010-06-05 21:57 It seems there is no bin/autospec with RSpec 2. So I got it running simply with $ autotest Been looking at instructions here http://wiki.github.com/dchelimsky/rspec/autotest-integration And here http://ph7spot.com/musings/getting-started-with-autotest But... $ RSPEC=true autotest loading autotest/cucumber_rspec Error loading Autotest style autotest/cucumber_rspec (no such file to load -- autotest/rspec). Aborting. What do I do here? I want to run it in "only rspec" mode for the time being. Also if I try to add the "redgreen" plugin # /.autotest require "autotest/restart" $ autotest loading autotest/cucumber style: Cucumber /Users/kristianconsult/.rvm/gems/ruby-1.9.2-head/gems/redgreen-1.2.2/ lib/redgreen/autotest.rb:6:in `
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
Autotest::Restart MODULE Autotest::Timestamp Methods ::add_discovery ::add_hook ::autodiscover ::new ::options ::parse_options ::run ::runner #add_exception #add_mapping #add_sigint_handler #add_sigquit_handler #all_good #clear_exceptions #clear_mappings #consolidate_failures #exceptions #files_matching #find_files #find_files_to_test #get_to_green #handle_results #hook #known_files #make_test_cmd #new_hash_of_arrays #old_run_tests #options #path_to_classname #remove_exception #remove_mapping #reorder #rerun_all_tests #reset #restart #ruby #ruby_cmd #run #run_tests #test_files_for #wait_for_changes Files History.txt Manifest.txt README.txt how_to_use_zentest.txt example.txt Class/Module Index Quicksearch Autotest Autotest::AutoUpdate Autotest::Bundler Autotest::Isolate Autotest::Once Autotest::Preload Autotest::RCov Autotest::Restart Autotest::Timestamp FunctionalTestMatrix Module Multiruby UnitDiff ZenTest ZenTestMapping No matching classes. Autotest Autotest continuously scans the files in your project for changes and runs the appropriate tests. Test failures are run until they have all passed. Then the full test suite is run to ensure that nothing else was inadvertantly broken. If you want Autotest to start over from the top, hit ^C once. If you want Autotest to quit, hit ^C twice. Rails: The autotest command will automatically discover a Rails directory by looking for config/environment.rb. When Rails is discovered, autotest uses RailsAutotest to perform file mappings and other work. See RailsAutotest for details. Plugins: Plugins are available by creating a .autotest file either in your project root or in your home directory. You can then write event handlers in the form of: Autotest.add_hook hook_name { |autotest| ... } The available hooks are listed in ALL_HOOKS. See example_dot_autotest.rb for more details. If a hook returns a true value, it signals to autotest that the hook was handled and should not continue executing hooks. Naming: Autotest uses a simple naming scheme to figure out how to map implementation files to test files following the Test::Unit naming scheme. Test files must be stored in test/ Test files names must start with test_ Test class names must start with Test Implementation files must be stored in lib/ Implementation files must match up with a test file named test_.*implem