Migration from QTP to Sahi

nv99

We have been using QTP for our projects, now we like to implement sahi tool for our new projects. I'm Automation Test Lead, We have explored sahi and would find it is one of good tool but we have following doubts :

1) We have 1000 TCs for Sanity, Integration & System Testing, Would it possible to automate
these kind of Tcs using Sahi ?
2) What are the best practices using Sahi ?
3) How we can structure Test cases in Sahi, like in QTP we'r using Actions for small functionality script and one main driver script which call all these funtionality and made end to end testing.
4) How would we structure 1000 TCs using sahi so it is easy maintainable.
5) What is the floting licence price ?
6) Does sahi have following features which is in QTP
- Recovery Scenario
- Error handling
- Environment Variable
- Get Current Script/Step pass/fail status
- Custom Reporting

Thanks & Regards,
NV

globalworming

Hi

1) If its done through a web interface, it can be tested with sahi
2) http://sahi.co.in/forums/viewtopic.php?id=2308
I personally really loved the page object pattern and Sahi in combination with a CI tool
3) You can have your test as a huge single file or refactor and break it down to small functions and readable code
4) Stucture as you like, everything has its disadvantages. A tree/ folder structure isn't the best way to sort scripts, but you may have nothing else. We structure or script by functionality (eg. folder for User Account Handling, a folder for search function tests ..)
5) Floating licence? It Open Source or 500 bucks for Sahi Pro, better ask Narayan about a floating licence
6) Yes

Regards
Wormi

nv99

Hello Wormi,

Thanks for quick responce.

Link which you provided here is not working.

Would you please eloborate more in details regarding structure. What are sahi command which will useful to implement structure ? Would you please provide sample strcture and best practice tutorial.

Thanks & Regards,
NV

globalworming

I did write something about page objects and the testrunner...
http://wiredworm.blogspot.de/2012/05/page-objects.html
as well as dasspunk
http://qualityshepherd.com/2012/05/javascript-page-object-pattern-for-sahi/
sahi forum post: http://sahi.co.in/forums/viewtopic.php?id=3896
and the best practices http://sahi.co.in/forums/viewtopic.php?id=2308


there is not much structure in my projects, I usually have

+test-project-root 
|- build.xml (suite starting for continous integration tool)
|- suite files
|- suite properties files (environment, initJs, globals etc)
|-+ bin
| | executables (for videocast/screenshot/sending mail/puttig browser to maximum witdth/height etc)
|
|-+ page-object-dir
| |- page-object-javascript-files
|
|-+ data-dir
| |- constant-dom
| |- dynamic-dom 
| |- generic-data (like csv, text etc)
| |- includeHeader.sah
|
|-+ functions-dir
| |- javascript functions (everthing which can not be paired with a distinct page object)
| |- testrunner.js
| |- prototypes (like the Page prototype)
|
|-+ target (test results go here)
| 
|-+ test-scripts-dir
  |-+ tests and subfolders as logic dictates
    |- UserAccountManagementTests
    |- OrderTest
    |- NewsletterTests

Structure your tests as you like. Use _include("includeHeader.sah") in every testscript (relativ path!). Includeheader.sah includes every function or data in the project, so its a list of _include(file).

Do you have further questions. Which detail should I explain more?

Regards
Wormi

nv99

Hello Wormi,

Thank you so much for your quick responce.

I'm looking in to resources you provided and have following queries .

1. Is above structure you provided that uses Sahi open source or Sahi Pro ?
2. Would you please let me know floating licence price ?

Thanks & Regards,
NV

globalworming

1. Sahi Open Source (but this doesn't matter as both can use the same concept)
2. As I said, write a mail to Narayan, I really don't know anything about it...

And I don't really think you need Sahi Pro, Sahi OS is setting you no boundaries. When you are missing a Sahi Pro feature, there are lots of ways to achive the functionality with different tools