janekk

I don't think so. It failed with Silverlight, and was nasty with ASP.NET webforms. Microsoft now champions ASP.NET MVC on the server and TypeScript on the client. They also use TypeScript to write huge JavaScript apps for consumers.

I'm worried this does not put usability first. In the example Edit form, I noticed two problems: 1) the radio button labels have not been linked using 'for' to the buttons, so clicking on them does nothing. 2) Hovering my mouse over the first address line text box causes it to move down away from my mouse! Errors like these will cause a lot of entry mistakes.

Braintree did not do AMEX in USD, last I talked to them a couple of months ago. How did you get this working? I'm very interested!

Thanks thairu, patrick has sent me an invite.

USD charging is definitely essential for SaaS selling to the US.

D'oh, I had no idea, and here I am already having spent months talking to NAB in order to charge USD and support AMEX. Stripe seems a lot cheaper too in terms of fees.

Stripe AU supports AMEX and USD charges, right?

Ian, I agree that's the right mind frame to be in, but I notice they (DevExpress) didn't address it in their demo or docs.

They have a 'wait' function that waits for a period of time, but this is just a sign of bad test writing and something sure to break when testing against different browsers or environments (localhost v.s. staging).

I like the visual method of writing scripts, but having used Selenium + SauceLabs.com on a real app and dealing with functional browser tests every day, I'm concerned about:

* Timing issues; most of the time spent writing functional tests is knowing when to wait for the next click (e.g. waiting for AJAX response and change in a certain DOM element)... and doing this in a clean way (e.g. WebDriverWait conditions instead of putting Sleep(1000) everywhere).

* Ability to expand the tests to do other things; for example, Selenium can take screenshots of the browser window because it works at a lower level. We use this for regression testing our web pages.

I'm in the 'something similar' camp. This is functional testing. I use Selenium, an open source library for automating browsers via plugins.

Personally I find it much more useful than unit/integration tests because while those test the programmer's understanding of his own code, functional tests actually drive the app, perform normal user actions by driving the GUI. For example, you could have all of your unit tests passing but without functional tests, your OK button may appear off-screen and you wouldn't know.

It is annoying when you make changes to your app because test runs take much longer than unit tests, so I have one general test that I run after a refactor, and then a full suite that runs after commit.