search for: test_test

Forgive me for asking a trivial question on this list, but being new to Ruby/Ruby on Rails, I''m not sure where to start.... I''m trying to connect to a postgresql server: My database.yml contains: test_test: adapter: postgresql database: test_test username: testuser password: resutest host: testpgserver port: 5432 encoding: UTF8 min_messages: warning The database is setup and talking with Java and Perl from the same client as I''m trying to use Ruby on Rails on. The command...

I just saw Marcel''s change to assert_difference that changes the method API to take a string param that is evaled in a lambda. http://dev.rubyonrails.org/changeset/6693 I much preferred the old API, since it''s simple enough to pass a lambda. Passing a string means the lambda is in the wrong scope and doesn''t have access to objects in the test case scope. For an

...ler. class StacktestController; def rescue_action(e) raise e end; end class StacktestControllerTest < Test::Unit::TestCase def setup @controller = StacktestController.new @request = ActionController::TestRequest.new @response = ActionController::TestResponse.new end def test_test process :test #assert_success #assert_rendered_file ''test'' end end ----- $ rake (in /home/Gul/stackleveltest) ruby1.8 -Ilib:test -e0 ruby1.8 -Ilib:test -e0 -rtest/functional/stacktest_controller_test Loaded suite -e Started E Finished in 0.049008 seconds. 1...

Hi David, >> Otherwise I''m fully committed to getting 0.10 out. >> When it is out, I''d recommend getting it into your >> development app as soon as you can. Any idea of timeframe to a 0.10 alpha release? Kind Regards Neville

...rors ---------------------------- the second snippet seems identical, but it yields a failed assertion: ---------------------------- class User < ActiveRecord::Base ... validates_confirmation_of :password ... ________________________________ class UserTest < Test::Unit::TestCase ... def test_test u = User.new( :username => "newbob", :password => "newpassword", :email => "newbob@mcbob.com" ) u.password_confirmation = "newpassword" assert u.save #(this is line 17) end --------------------------...

...sleeping...) Here's a load of output which I hope could help identify the cause(s) of this behaviour if anyone's interested. I ran a dtrace script against the sshd processes on the machine and noticed one reading & writing as I pasted in a large quantity of text to a file (/tmp/sshd.test_test): # ./opensnoop -n sshd UID PID CMD D BYTES FILE 12962 9649 sshd R 1056 <unknown> 12962 9649 sshd W 1022 /devices/pseudo/clone at 0:ptm 12962 9649 sshd R 480 <unknown> 12962 9649 sshd W 386 /devices/pseudo/clone at 0...

...ing to use a namespace with my model class such as Namespace::Test so I run: script/generate model namespace/test create app/models/namespace create test/unit/namespace create test/fixtures/namespace create app/models/namespace/test.rb create test/unit/namespace/test_test.rb create test/fixtures/namespace/tests.yml create db/migrate create db/migrate/001_create_namespace_tests.rb However, the unit test has the line "fixtures :tests" which causes the test to fail because it looks for the fixture file in test/fixtures/tests.yml instea...

...the only valid usecase for "export -p" is to eval the output. > > $ eval $(export -p); echo OK > OK > > Without this patch the following test does error out with: > > test.py: > import os > os.environ["test-test"]="test" > os.environ["test_test"]="test" > os.execv("./dash", [ './dash', '-c', 'eval $(export -p); echo OK' ]) > > $ python test.py > ./dash: 1: export: test-test: bad variable name > > Of course the results can be more evil, if the environment variable > name...

...with Postgresql 8,2.5 (latest stable version) Steps taken 1. Download Postgresql 1.82 and installed successfully 2. Edited my Database.yml development: adapter: postgresql database: test_development username: postgres password: xxx host: localhost test: adapter: postgresql database: test_test username: postgres password: xxx host: localhost production: adapter: postgres database: test_production username: root password: xxx host: localhost I had earlier created an appropriate migration file then rake db:migrate Result : rake aborted! database configuration specifies...

...here. I do not know if it is a bug of my package or testthat or the ALTREP implementation of R or possibly the interaction between them. I will appreciate if anyone can shed light on it. Here is the link to my package test file: https://github.com/Jiefei-Wang/AltWrapper/blob/master/tests/testthat/test_test.R Best, Jiefei [[alternative HTML version deleted]]