The same test is continuing to fail in the exact same way. It is not intermittent, the test has failed every time I have run it since I discovered the issue. I am 99% confident that it is a new bug on your end, introduced sometime between 3/17/2011 (the last time tests were run and they passed) and 3/31/2011 (first time the tests were run since 3/17, and the test fails).

Thank you,
Michael Kuehl

It is a cucumber test, so I'm not sure how helpful this will be:

@shouldwork @failure_case Scenario: Try to create a paid account but with bad credit card info

And I am on the home page
When I follow "See Plans & Pricing"
And I follow "Sign Up"
And I fill in "email" with "email@example.com"
And I fill in "First name" with "Billy"
And I fill in "Last name" with "Bob"
And I fill in "password" with "secret"
And I fill in "password confirmation" with "secret"
And I fill in unauthorized credit card information
And I press "Sign Up"
Then I should see "1 error prohibited this user from being saved"
Then I should see "Forced storage failure"

The problem is that since there are no errors reported from Chargify on the subscription create (even though the create does fail with a 422 error), the error text "Forced storage failure" (which chargify used to return) is not shown.

I just ran the test again, as I have been every day since it started failing, and today the test passed. Absolutely nothing has changed on my end - from when it was working, to when it started failing, to now when it works again. Did you guys fix a bug on your end?