Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TestCafé: Web Testing Framework

testcafe.devexpress.com

Post reply on HN
Print view View original

21–30 of 32 posts

Re: TestCafé: Web Testing Framework

#21

Post by hugs »

davidjgraph wrote: post #16
hugs wrote: post #8

"Yes, we've filed for a patent" "TestCafé loads websites via a proxy, thus allowing its engine to inject scripts that can access and manipulate the Document Object Model" 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. "While loading via proxy is not a new idea, our implementation is unique…

The US patent office does not care/have the resources/have a clue how to enforce that patents are non-novel and/or obvious. It is an entirely corrupt system driven by a mass of lawyers, all encouraging their clients to build patent portfolios for "defence". If you want to combat a patent, the best stage to do this is during the application stage, it's far harder to combat it after it's approved. For those that aren't…

Thanks, I'll look into it. This is a serious issue.

Re: TestCafé: Web Testing Framework

#23

Post by hugs »

polyvisual wrote: post #19
hugs wrote: post #12

Earlier quoted context omitted.

I'd also recommend they reach out to Selenium developers and having a conversation with them to see if what they've done is really patentable. [Disclosure: I created Selenium]

Thanks for creating Selenium hugs .

:-) Although I kickstarted the project, I can't take a lot of credit for what it has become. It's a huge project now, with many people involved. Now, I'm just the crazy old uncle who can tell a good story about "the olden days". In the spirit of giving credit where credit is due, Paul Hammant is the one who came up with the HTTP proxy JS injection technique. Dan Fabulich, Nelson Sproul, and Patrick Lightbody rewrote it and refined it. (Some sources: http://paulhammant.com/blog/selenium.html/ http://docs.seleniumhq.org/about/history.jsp)

Re: TestCafé: Web Testing Framework

#24

Post by sergiotapia »

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.

What benefits does TestCafe bring against Selenium? What's the elevator pitch?

Re: TestCafé: Web Testing Framework

#25

Post by sergiotapia »

hugs wrote: post #12
wldlyinaccurate wrote: post #11

I skim-read their website and watched a good chunk of their video. I still have no idea what this actually is, and why I would use it over my existing toolset (Behat, Selenium + WebDriver, CasperJS, etc). If any DevExpress guys/gals are reading this, please consider making a shorter (2-3 min) video showing some tests being written and run.

I'd also recommend they reach out to Selenium developers and having a conversation with them to see if what they've done is really patentable. [Disclosure: I created Selenium]

Thank you for your hard work! Hugs from Bolivia!

Re: TestCafé: Web Testing Framework

#27

Post by [deleted] »

davidjgraph wrote: post #16
hugs wrote: post #8

"Yes, we've filed for a patent" "TestCafé loads websites via a proxy, thus allowing its engine to inject scripts that can access and manipulate the Document Object Model" 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. "While loading via proxy is not a new idea, our implementation is unique…

The US patent office does not care/have the resources/have a clue how to enforce that patents are non-novel and/or obvious. It is an entirely corrupt system driven by a mass of lawyers, all encouraging their clients to build patent portfolios for "defence". If you want to combat a patent, the best stage to do this is during the application stage, it's far harder to combat it after it's approved. For those that aren't…

[deleted]

Re: TestCafé: Web Testing Framework

#28

Post by SkyMarshal »

hugs wrote: post #21
davidjgraph wrote: post #16

Earlier quoted context omitted.

The US patent office does not care/have the resources/have a clue how to enforce that patents are non-novel and/or obvious. It is an entirely corrupt system driven by a mass of lawyers, all encouraging their clients to build patent portfolios for "defence". If you want to combat a patent, the best stage to do this is during the application stage, it's far harder to combat it after it's approved. For those that aren't…

Thanks, I'll look into it. This is a serious issue.

Peer-To-Patent is another good one - http://peertopatent.org/

Re: TestCafé: Web Testing Framework

#29

Post by jolt »

sergiotapia wrote: post #24

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. What benefits does TestCafe bring against Selenium? What's the elevator pitch?

What was the hassle you had with using Selenium. Only the configuration?

Re: TestCafé: Web Testing Framework

#30

Post by jolt »

hugs wrote: post #9
jolt wrote: post #2

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.

It sounds like their approach is the same one we took with the first version of Selenium. The approach is JavaScript injection through an HTTP proxy. Because of the same origin policy and JavaScript security model, we abandoned this approach when moving to Selenium 2. Selenium 2 goes for the most native approach for clicks and key events. (Continuing in that native-is-better approach, I'm now experimenting with robot…

Thank you. From what i have gathered here in the comments, it seems that I need to look into Selenium.
Post reply on HN