Alright, thanks for your help guys. I found the problem. I debugged
the code and I found the right header "HTTP_ACCEPT" in its request
object. Rails uses this header to response back.
Thanks
Chamnap
___
rspec-users mailing list
rspec-users@rubyforge.org
On Aug 16, 2009, at 8:01 PM, Chamnap wrote:
I did the same thing as you did, but it doesn't work. The respond_to
method still responses back in "application/xml". Any idea?
Did you spell it ACCEPT ( all caps )?
On Aug 15, 8:49 pm, David Chelimsky wrote:
On Sat, Aug 15, 2009 at 5:35 AM, C
On Aug 17, 9:19 am, Stephen Eley wrote:
> It sounds like you're pretty sure your code is correct and your tests
> are broken. Does the application work outside of the RSpec tests?
> Can you hit it with, say, 'curl' with the json Accept header and
> determine if it does the right thing?
Well, I c
On Sun, Aug 16, 2009 at 9:01 PM, Chamnap wrote:
> I did the same thing as you did, but it doesn't work. The respond_to
> method still responses back in "application/xml". Any idea?
It sounds like you're pretty sure your code is correct and your tests
are broken. Does the application work outside
I did the same thing as you did, but it doesn't work. The respond_to
method still responses back in "application/xml". Any idea?
On Aug 15, 8:49 pm, David Chelimsky wrote:
> On Sat, Aug 15, 2009 at 5:35 AM, Chamnap wrote:
> > I tried several hours to mock. What I want is basically to send "http
On Fri, Aug 14, 2009 at 9:13 AM, Peter
Fitzgibbons wrote:
> Hello All,
>
> a-la cucumber:
> Feature: Spec runs Integrations
> Scenario: When code changes, Integration specs run
> Given a rails app with controllers, models, view, helpers
> And a spec under spec/integration
> When code
On Sun, Aug 16, 2009 at 2:46 AM, Brandon
Olivares wrote:
> Hi,
>
> I'm really sorry, never mind on the matcher. I guess I remembered
> incorrectly how to set the subject.
>
> Is:
>
> Subject { @game }
It's with a lowercase 's':
subject { @game }
But if you call the subject method without a block