fers a detailed approach to address the underlying problem
All without a hint of condescension.
Thank you very much! This will help improve my code in many ways
beyond the present problem.
--Dean
On Jul 10, 6:00 am, David Chelimsky wrote:
> On Jul 8, 2011, at 5:37 PM, Dean wrote:
>
>
&
are in
subdirectories, e.g.:
app/controllers/admin/testimonials_controller.rb
and
app/views/admin/testimonials/new.html.erb
Should my tests say something like:
get 'admin/testimonials/new' instead of get 'new'? Or am I making a
less subtle mistake?
Thanks,
Dean
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
default
Using the default profile...
database configuration does not specify adapter
(ActiveRecord::AdapterNotSpecified)
...
followed by
rake aborted!
Command failed with status (1): [bundle exec
/System/Library/Frameworks/Rub...]
Any suggestions on what I should try next?
T
where to look.
Any suggestions on whether that might be the issue and if so, how to
address it?
Thanks once more...
Dean
Luis Lavena wrote in post #960735:
> On Thu, Nov 11, 2010 at 9:49 AM, Dean Richardson
> wrote:
>> presence of the sqlite3-ruby gem and other associated dependencies. Th
hat's so
different about the genlighten app's configuration/setup that it fails
to find sqlite3 (if that's even what's really going on...)
--Dean
BTW, your suggested fix to the "test:" section in my database.yml file
for using mysql on my test database worked flaw
Hi Luis:
Thanks for the rapid response. I'll work on your MySQL fix... in the
meantime, what further details can I provide regarding the sqlite3
adapter issue?
--Dean
Luis Lavena wrote in post #960735:
> On Thu, Nov 11, 2010 at 9:49 AM, Dean Richardson
> wrote:
>> presen
s machine
(MBP) that use sqlite3 successfully.
Is there a version of sqlite3 that might help eliminate the error but
which doesn't require Ruby 1.9.1? Or is the upgrade path the only one
that's likely to work for me?
Again, thanks for your help...
--Dean
Paul Nelligan wrote in post
e of the fixes I've found so far there seem to
help.
Any suggestions for how to make either test database approach (sqlite3
or mysql) work would be greatly appreciated.
Thanks again for your help,
Dean Richardson
David Chelimsky wrote in post #960323:
> On Nov 9, 2010, at 6:38 A
David Chelimsky wrote in post #960173:
> On Nov 8, 2010, at 12:40 PM, Dean Richardson wrote:
>
>> rspec-rails (1.3.2)
>>
>> I started by installing rspec-rails 1.3.2, then cucumber-rails 0.3.2,
>> then database_cleaner and webrat. I then tried to run rake spec an
he
rspec-2.1.0 gem.
But when I ran rake spec again, I got the same error message as before.
Should I have installed an earlier version of the rspec gem?
Thanks,
Dean Richardson
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
r
Exactly the kind of monkey patch I was looking for - thanks Luis !
I also saw you could edit the spec_server file to make
if options[:daemon]
into
if options[:daemon] and false or something similar, but a no touch
solution like yours is nice, and thanks for the Ctrl-Break tip.
D
Luis Lavena
open3 and win32-process already but no dice.
Dean
> rake spec:server:start
(in C:/ChessOnRails/trunk)
Starting up spec server.
Loading Rails environment
Ready
script/spec_server:81:in `fork': fork() function is unimplemented on
this machine (NotImplementedErr
or)
from script/spec_s
12 matches
Mail list logo