JadeLiquid Software has released LiquidTest 2.0, whose new features include new IDE integrations, languages and major core engine improvements. LiquidTest now ships with specific support for Web 2.0 frameworks such as ExtJS, Dojo, GWT, ASP.NET, and more.
To learn how LiquidTest is different from other Web Application Testing products, visit JadeLiquid at:
What tools and/or techniques do you currently use to test web applications? What are the major problems you have in testing web applications, and how do you get around them?
Doesn't seem from the page that it allows using the cloud to map out tests.
Starting up and shutting down the browser is a major overhead. Google does these sorts of tests routinely on their servers. I can only conclude that this product doesn't server big customers, or isn't holding big customers hands enough and giving them direction on how to take web app testing seriously.
Thank you for your considered response John. In many ways I agree with what you are saying. We really need to work on our "end to end" documentation. Even though it is not clear from our front page, pushing tests out over a grid/network/cloud is a "native" feature. Given that LiquidTest tests are JUnit (or NUnit depending on your platform/environment) pushing out over a network for scaled parallel execution is straight forward. Internally we use Team City to do this exact task. Any framework that is capable of running JUnit/NUnit tests can execute LiquidTest test cases. That all being said, we need to work on our communication to get this point across and I thank you sincerely for your feedback. It is extremely helpful. It is not always easy to "see" from the inside out.
With respect to the starting of the web browser, the overhead is minimal in the grand scheme of things. We reuse the browser once started, so the overhead is a one-off hit, rather than a load-unload process over and over.
Anthony Scotney CEO of JadeLiquid (LiquidTest developers)
I am pretty sure the context for my comments comes from a presentation I watched by a Google Test Engineer, who did his undergrad at Notre Dame. Maybe it was Jason Huggins? I don't know. Googling around, it appears Jason Huggins and Simon Stewart both have done stuff with Selenium, and that Jason now runs a company that sells a product called Sauce that allows for cloud-based testing.
I don't know if Jason went to Notre Dame or not, but I remember the talk I watched online that the guy was a Googler from Notre Dame. I think he also worked at ThoughtWorks before Google...
Sorry my memory is fading.
I am pretty sure Google advocates constantly shutting down the browser and restarting it to preserve the true idea of a unit test. Wish I could find the exact talk to prove my comments correct.
Previous Topic
