11–20 of 32 posts
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 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.
"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…
"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…
"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…
"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…
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 aware of the StackExchange patents site [0], this is the best site I'm currently aware of for collecting evidence against patent applications. I would encourage you to actively seek out this patent application, start a thread on it and submit evidence against it.
The US needs a cultural change on patents, to make it clear that the patent system is corrupt and companies that file software related/non-original patents as an excuse to not having to innovate any further/at all need to be shunned.
I'd like to see how their offering stands up to that.
(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!)
"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…
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]
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 inste…
This can be answered in a fairly simple way. How does your user know when to proceed? What changes?