On 23 November 2011 00:57, Justin Ko wrote:
>
> On Nov 22, 2011, at 4:52 PM, Andrew Premdas wrote:
>
>> On 22 November 2011 20:31, Ash Moran wrote:
>>> Hi
>>>
>>> I've worked on a couple of Rails 3 apps recently and the test feedback loop
>>> is killing me. With no modifications, it takes 15-25
On Nov 22, 2011, at 4:52 PM, Andrew Premdas wrote:
> On 22 November 2011 20:31, Ash Moran wrote:
>> Hi
>>
>> I've worked on a couple of Rails 3 apps recently and the test feedback loop
>> is killing me. With no modifications, it takes 15-25 seconds to run a single
>> example. I've avoided Spo
On 22 November 2011 20:31, Ash Moran wrote:
> Hi
>
> I've worked on a couple of Rails 3 apps recently and the test feedback loop
> is killing me. With no modifications, it takes 15-25 seconds to run a single
> example. I've avoided Spork so far, but I've tried Spin[1]. Spin shaves a few
> secon
Hi
I've worked on a couple of Rails 3 apps recently and the test feedback loop is
killing me. With no modifications, it takes 15-25 seconds to run a single
example. I've avoided Spork so far, but I've tried Spin[1]. Spin shaves a few
seconds off but it's still agonising. I've also experimented
Mohnish J. wrote in post #1033006:
> Sidu Ponnappa wrote in post #1032900:
>>> I'm getting a common error for all such defined methods saying that>
>> `database_name.table_name does not exist`. Well , this is true but how>
>> should is
>> it really making a difference?, and how to get a work around
If your tests run in db transaction, you will not see the records when
using javascript test adapter, like selenium. Refer to the capybara's
README how to solve that, if this is the problem.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://ru
Hi all,
I may be missing something simple here, but I'm having problems with
attempting to get a javascript request test going. I'm not sure if
this is the correct place to ask but perhaps someone will be able to
direct me to the right place if not.
The problem I'm having is that in my before(:ea
