"Yes, we've filed for a patent"<p>"TestCafé loads websites via a proxy, thus allowing its engine to inject scripts that can access and manipulate the Document Object Model"<p>That's exactly how Selenium 1 worked when we created it 9 years ago. It also sounds like the approach used in Sahi, Windmill, JsTestDriver -- other web testing tools. Not cool.<p>"While loading via proxy is not a new idea, our implementation is unique. Our framework is the only one that automatically configures that proxy and allows direct communication with the page via JavaScript."<p>I look forward to reading your patent application.
I'm currently watching the 27minute video. I was expecting a quick sample of what TestCafe does, but it is a full-on tutorial of using all their features. Also it goes into a VERY deep yet simple level (like here's how to change the port#).<p>I'd recommend a shorter, marketing style video just showing why TestCafe is great. I haven't gotten there yet, at more than 5 minutes in...
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:<p>* 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).<p>* 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 skim-read their website and watched a good chunk of their video. I <i>still</i> have no idea what this actually is, and why I would use it over my existing toolset (Behat, Selenium + WebDriver, CasperJS, etc).<p>If any DevExpress guys/gals are reading this, please consider making a shorter (2-3 min) video showing some tests being written and run.
We've been using Selenium to test a large enterprise ASP.Net webforms application and it's been kind of a hassle. Configuration was horrible but once that's out of the way it's sort of straightforward.<p>What benefits does TestCafe bring against Selenium? What's the elevator pitch?
We're on the verge of running a Selenium Grid server with a ~1000 Selenium nodes connected to it.<p>I'd like to see how their offering stands up to that.<p>(Actually, I don't know how Selenium will stand up to that... maybe I should have left this comment until I've got the results!)
Haven't used it myself, but i would love to hear from someone who has used this, or something similar.
How useful is this kind of testing? I'm thinking that tests would have to be re-recorded a lot, if this is used while developing the site.