수있는 사람의 서비스 문제 해결 팁? 관련 레일 명령의 다음과 같은 순서로레일 '레이크 시험은'즉시 프로젝트가 여기
새로운 레일을 생성 한 후 두 번 테스트를 실행 rake task 'test'를 두 번 실행하십시오. 내가 어디로 잘못 갔니?
로그가 여기에 있습니다 :
perrys-MacBook-Pro:rails_projects perry_mac$ rails new test6
create
create README
create Rakefile
create config.ru
create .gitignore
create Gemfile
create app
create app/controllers/application_controller.rb
create app/helpers/application_helper.rb
create app/mailers
create app/models
create app/views/layouts/application.html.erb
create config
create config/routes.rb
create config/application.rb
create config/environment.rb
create config/environments
create config/environments/development.rb
create config/environments/production.rb
create config/environments/test.rb
create config/initializers
create config/initializers/backtrace_silencers.rb
create config/initializers/inflections.rb
create config/initializers/mime_types.rb
create config/initializers/secret_token.rb
create config/initializers/session_store.rb
create config/locales
create config/locales/en.yml
create config/boot.rb
create config/database.yml
create db
create db/seeds.rb
create doc
create doc/README_FOR_APP
create lib
create lib/tasks
create lib/tasks/.gitkeep
create log
create log/server.log
create log/production.log
create log/development.log
create log/test.log
create public
create public/404.html
create public/422.html
create public/500.html
create public/favicon.ico
create public/index.html
create public/robots.txt
create public/images
create public/images/rails.png
create public/stylesheets
create public/stylesheets/.gitkeep
create public/javascripts
create public/javascripts/application.js
create public/javascripts/controls.js
create public/javascripts/dragdrop.js
create public/javascripts/effects.js
create public/javascripts/prototype.js
create public/javascripts/rails.js
create script
create script/rails
create test
create test/fixtures
create test/functional
create test/integration
create test/performance/browsing_test.rb
create test/test_helper.rb
create test/unit
create tmp
create tmp/sessions
create tmp/sockets
create tmp/cache
create tmp/pids
create vendor/plugins
create vendor/plugins/.gitkeep
perrys-MacBook-Pro:rails_projects perry_mac$ cd test6
perrys-MacBook-Pro:test6 perry_mac$ bundle install
Fetching source index for http://rubygems.org/
Using rake (0.9.2)
Using abstract (1.0.0)
Using activesupport (3.0.9)
Using builder (2.1.2)
Using i18n (0.5.0)
Using activemodel (3.0.9)
Using erubis (2.6.6)
Using rack (1.2.3)
Using rack-mount (0.6.14)
Using rack-test (0.5.7)
Using tzinfo (0.3.29)
Using actionpack (3.0.9)
Using mime-types (1.16)
Using polyglot (0.3.1)
Using treetop (1.4.9)
Using mail (2.2.19)
Using actionmailer (3.0.9)
Using arel (2.0.10)
Using activerecord (3.0.9)
Using activeresource (3.0.9)
Using bundler (1.0.15)
Using rdoc (3.8)
Using thor (0.14.6)
Using railties (3.0.9)
Using rails (3.0.9)
Using sqlite3 (1.3.3)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
perrys-MacBook-Pro:test6 perry_mac$ rake test
perrys-MacBook-Pro:test6 perry_mac$ rails generate controller Gohere left right up down
create app/controllers/gohere_controller.rb
route get "gohere/down"
route get "gohere/up"
route get "gohere/right"
route get "gohere/left"
invoke erb
create app/views/gohere
create app/views/gohere/left.html.erb
create app/views/gohere/right.html.erb
create app/views/gohere/up.html.erb
create app/views/gohere/down.html.erb
invoke test_unit
create test/functional/gohere_controller_test.rb
invoke helper
create app/helpers/gohere_helper.rb
invoke test_unit
create test/unit/helpers/gohere_helper_test.rb
perrys-MacBook-Pro:test6 perry_mac$ rake test Loaded suite /Users/perry_mac/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/rake_test_loader
Started
Finished in 0.002747 seconds.
0 tests, 0 assertions, 0 failures, 0 errors, 0 skips
Test run options: --seed 15229
Loaded suite /Users/perry_mac/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/rake_test_loader
Started
....
Finished in 0.438403 seconds.
4 tests, 4 assertions, 0 failures, 0 errors, 0 skips
Test run options: --seed 9266
perrys-MacBook-Pro:test6 perry_mac$
... 그리고 RVM 정보 수율 :
perrys-MacBook-Pro:test6 perry_mac$ rvm info
ruby-1.9.2-p290:
system:
uname: "Darwin perrys-MacBook-Pro.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 i386"
bash: "/bin/bash => GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0)"
zsh: "/bin/zsh => zsh 4.3.9 (i386-apple-darwin10.0)"
rvm:
version: "rvm 1.6.23 by Wayne E. Seguin ([email protected]) [https://rvm.beginrescueend.com/]"
ruby:
interpreter: "ruby"
version: "1.9.2p290"
date: "2011-07-09"
platform: "x86_64-darwin10.8.0"
patchlevel: "2011-07-09 revision 32553"
full_version: "ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin10.8.0]"
homes:
gem: "/Users/perry_mac/.rvm/gems/ruby-1.9.2-p290"
ruby: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290"
binaries:
ruby: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290/bin/ruby"
irb: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290/bin/irb"
gem: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290/bin/gem"
rake: "/Users/perry_mac/.rvm/gems/ruby-1.9.2-p290/bin/rake"
environment:
PATH: "/Users/perry_mac/.rvm/gems/ruby-1.9.2-p290/bin:/Users/perry_mac/.rvm/gems/[email protected]/bin:/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290/bin:/Users/perry_mac/.rvm/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/X11/bin"
GEM_HOME: "/Users/perry_mac/.rvm/gems/ruby-1.9.2-p290"
GEM_PATH: "/Users/perry_mac/.rvm/gems/ruby-1.9.2-p290:/Users/perry_mac/.rvm/gems/[email protected]"
MY_RUBY_HOME: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290"
IRBRC: "/Users/perry_mac/.rvm/rubies/ruby-1.9.2-p290/.irbrc"
RUBYOPT: ""
gemset: ""
perrys-MacBook-Pro:test6 perry_mac$
감사합니다. Adam. 나는 동의한다. 오래 전에 그것을 보았지만 여기를 업데이트하기에는 너무 게으른 것입니다. 120+ 조회수가 가장 인기있는 질문이 아니지만 다른 사용자도 혼란 스러울 수 있음에 동의합니다. 귀하의 답변에 감사드립니다. 왜 단위 테스트와 기능 테스트가 실행 및 출력 측면에서 개별적으로 처리되는지는 잘 모르겠습니다. 나는 또한 단위 테스트와 기능 테스트가 그들의 테스트 데이터를 다르게 처리하기 전에 상당히 불투명하다. 기본적으로 나는 TDD에 대해 생각하지 못했다. 왜냐하면 많은 부분이 번거롭기 때문이다. 루비는 컴파일 된 언어가 아니기 때문에 TDD의 필요성을 이해하지만 상처를줍니다. –
... 내 의견보기 TDD를 사용해야하는 다른 이유가 많이 있다는 것을 깨달았지만 고통을 덜어주지는 않습니다. –