Selenium was jokingly meant as a cure for QTP? How effective has the cure been?

23 Sep

I had found that out some time ago in a social media post. Here’s a reference about it on wikipedia:

http://en.wikipedia.org/wiki/Selenium_(software)

How effective would you say the cure is?

I’d say making progress, but we’re not cured of QTP just yet…Appium + WebDriver + JSONWireProtocol is making that more achievable across all types of automation for the cure…right now we just lack a “WebDriver” for the desktop GUI. As we’ve got mobile covered (Appium, Selendroid, ios-driver, and other similar tools), and web was long covered by Selenium RC and WebDriver.

We kind of have for desktop: Twin project

https://code.google.com/p/twin/

https://www.youtube.com/watch?v=NiCCcf5HKQI

http://www.slideshare.net/videotuition/twin-automation-tool-automating-windows-applications-selenium-web-driver-grid

 

but it’s nowhere near the prominence of a household name as Selenium or Appium in regards to desktop GUI automation. I personally don’t know how well that tool works either as I’ve not tried it out yet. But until that tool gains prominence or a new project comes along, there will always be QTP and like commercial tools for the following:

  • desktop GUI automation
  • integrated or crossover automation that involves desktop + web/mobile
  • automation for things Selenium can’t control (HTTP authentication popup, file browse popup, download popups, etc. for which in OSS world you use tools like AutoIt or Sikuli with Selenium to bridge the gap)

I would say though that if I had to go with desktop GUI automation and wasn’t stuck on having to use an existing tool, I’d go for Twin and at same time improve it where and however I can.

Advertisements

One Response to “Selenium was jokingly meant as a cure for QTP? How effective has the cure been?”

  1. fijiaaron September 23, 2014 at 10:47 pm #

    It’s a great idea, but Twin looks like there hasn’t been any development on since 2011. Not that it isn’t worth investigating.

    I think you’re right that it’s about time we started working towards that goal, but Webdriver has been moving in the wrong direction — narrowing it’s use cases and shunning users and the “test” appellation.

    I think we need to think of an automation framework or protocol with various “drivers” of which Webdriver is only one (or rather, 3 — Firefox, IE, and Chrome.)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Pete Zybrick

Bell Labs to Big Data

Seek Nuance

Python, technology, Seattle, careers, life, et cetera...

TELLURIUM

New Era of Test Automation

Der Flounder

Seldom updated, occasionally insightful.

The 4T - Trail, Tram, Trolley, Train

Exploring Portland with the 4T

Midnight Musings

Thoughts on making art

Automation Guide

The More You Learn The More You Play...!

The Performance Engineer

Code.Test.Tune.Optimize.

humblesoftwaredev

Thoughts related to software development

Yi Wang's Tech Notes

A blog ported from http://cxwangyi.blogspot.com

Appium Tutorial

Technical…..Practical…..Theoretically Interesting

LinuxMeerkat

I swear! Meerkats can do Linux

PacketsDropped

Requeuing the packets dropped in my memory.

Two cents of software value

Writing. Training. Consulting.

@akumar overflow

wisdom exceeding 140 chars.

%d bloggers like this: