Page 1 of 1

Reusing a test suite from desktop to web based application

PostPosted: Wed Jul 02, 2014 8:37 pm
by JHerod
Evening

Hey eValid. If I have a bunch of tests for my desktop based application that has now been converted to a web based application, what percentage of those tests will run on the new app?

I mean, I want to reuse my test suite?

What do you think?

Thanks

Re: Reusing a test suite from desktop to web based applicati

PostPosted: Mon Jul 07, 2014 8:57 am
by eValid
JHerod wrote:Evening

Hey eValid. If I have a bunch of tests for my desktop based application that has now been converted to a web based application, what percentage of those tests will run on the new app?

I mean, I want to reuse my test suite?

What do you think?

Thanks


Hey JHerod, thanks for asking.

The answer depends a LOT on what kind of environment the pure-desktop version of your application was built in compared with how the web based version was built. For purposes of discussion, let's assume that both versions have identically the same structure (same pages, same pulldowns, same user inputs, etc.)

For a pure-desktop based application all of the tests will necessarily exist in "desktop mode" (also called Application Mode), and those tests are expressed in terms of positions on the desktop and actions by the user (keyboard and mouse).

Some of those scripts may play back OK on your web-based version of the application, and some may not. It is difficult to predict this.

If you have used development environment that supports both desktop and web realizations, then the chances are better. We have seen some such environments this is very easy, provide the web version is used in "Maximized" mode, but again, it is not a sure thing.

At the very least, assuming that both apps are organized the same way, you could use one instance of eValid in playback mode for the desktop version (using single step actions) to be the guide for recording fron an eValid instance that is running the web-based version. At least that way there'd be a one-to-one correspondence in the test cases.

-- eValid Support