QTP: Migration part 4

I started my test tool career about ten years ago with a custom tool in MS Access. Now ten years later I find this wonderful feature in MS Access 2003, create a web page with MS SQL Server underneath...

You can build a real handy GUI in just minutes...which I did (4 and counting...)

Almost done migration, have a few test scenarios to manually convert left...

QTP: Migration part 3

Puh...

Done converting Test Case Functions with my new Dictionary Object concept, works fine so far...

Next...create web GUIs to handle the database

QTP: Migration part 2b

Sorry...

You can see values of a Dictionary Object when debugging...

Add to Watch panel:

objMyDictionary.Item("MyParameter")

QTP: Migration part 2

Done converting xls -> SQL Server...so far everything seems OK

Last week I 'discovered' the Dictionary Object...seems perfect when to pass/get parameters from a function (I don't use Actions). So now I am converting my test case functions using Dictionary Object instead of ordinary variables.

+ Easy to add parameters
+ Allows optional parameters
+ Allows multiple output values
+ Since my test parameters are now in a table (pair-wise) I can have a Dictionary Object with the entire recordset (select parameter_name, parameter_value where test_case_id = ...) which is easy to merge with my global test parameters (test environment etc) and have it in my call to a test case.

Set objTCOutputData = MyTestCase (objTCInputData)

- Values in a Dictionary Object are not visible when debugging :-(

QTP: Migration part 1

I have always been a big fan of Excel, but last week when one of my test case files got corrupt after an update I decided it was to time to move forward...

...to have all my test data in MS SQL Server instead of xls-files.

So during this week I have been modifying my data model and created a database which will contain all my test case data. Currently I'm writing migration scripts which will transfer all my data from the xls-files to the new database...

QTP: Functions vs Actions

I started my QTP career with Actions but are now only using Functions. Why?

- All variables are shown when debugging (action parameters don't)
- Easier to add parameters
- Faster to load test that has only one Action (the default one)
- No need to bother where reusable Actions are located.
- Possible to edit the functions without have to load other test containing reusable actions

Conclusion: Faster, Easier and more cost effective...

...but it is also a matter of automation taste...