Tuesday, February 17, 2009

Populating Data on SAP server.

I was assigned this unique task of populating specific (P2P, Authorizations) data on SAP server. Specific data was required for testing purpose by both development and QA department. P2P transaction included the following parts:
Purchace Recquisition-> Purchase Order -> Goods Receipts -> Invoice Receipts -> Payments
I tried various options like writing simple vb script to connect to SAP Server like the following:

I also tried using QTP to capture SAP objects and rerun the script as many times as we needed. But QTP made the application extremely slow and required too much tweaking. We were able to generate 1000 records of P2P transactions in about 13 hours using QTP which was not enough for Performance testing. They needed millions of records per day. We were in a jinx when i found a document which mentioned about using in-build recording function by SAP and voila... It was so easy to record a transaction and the output was a vbs file which could be parameterized easily by getting values from Excel. The vbs file is very easy to understand and maintainable as well. Following are the steps to have recorded script:
1) Enable scripting on SAP Server.

2) Go To Script Recording and Playback from Customizing local layout in SAP GUI.

3) Start recording in SAP GUI after clicking the Record button on newly popped up Record window.

4) Once you are done with your recording open the vbs file saved.

5) Parameterize this file and you are ready to populate data on SAP server.

Mail me in case you have any issues regarding populating data on SAP Server using this method.

Monday, February 9, 2009

VSTS Test Edition for automated testing.

VSTS could be used for the following:
1) Unit testing
2) Web testing
3) Load Testing

Web test in VSTS could be used for automated functional testing. It records HTTP transactions and not API calls. The language used is C++ or VB.NET
Pros of using VSTS:
1) Parameterization of test data possible
2) Add validation points( called Validation Rules)
3) Script is reliable where frequent UI changes take place

Cons of using VSTS:
1) No UI, Database validation possible.
2) No Flow control or other programming constructs provided by other auotmation languages.
3) Does require higher skill set for functional testers.

Thus Microsoft VSTS is competing with HP QTP in terms of automated testing. But I feel VSTS has a long way to go still, looking at advantages QTP provides.