1<br />Automation Framework<br />
2<br />Test Automation Approach<br /><ul><li>The Test Script Modularity Framework
The Test Library Architecture Framework
The Keyword-Driven or Table-Driven Testing Framework
The Data-Driven Testing Framework
The Hybrid Test Automation Framework</li></li></ul><li>3<br />Test Automation Framework<br />	The most commonly implemente...
4<br />Test Script Modularity Framework<br />The test script modularity framework requires the creation of small, independ...
5<br />Test Library Architecture Framework<br />The test library architecture framework is very similar to the test script...
6<br />VBS files for Partitions<br />Partition in NexOSLibrary file<br />		1.Login				NexOS_Login.vbs	<br />		2.Applicatio...
7<br />VBS files for Generic Functions<br />Functionality		Library File<br />1.Datatable			DataTable.vbs<br />		2.Global		...
8<br />Data-Driven Testing Framework<br />Data-driven testing framework is incorporated in NexOS Project by inputting the ...
9<br />Configuration Settings<br />Environment Variables (read only data) are declared in Config.ini file<br />Following a...
ScreenshotRootpath
POS_Validation
TakeScreenshot</li></li></ul><li>10<br />Login Configuration<br />The user id, password (encrypted) and environment (URL) ...
11<br />Folder Structure<br />Test Plan consists of three main folders:<br />Development contain scripts under constructio...
12<br />Test Plan Structure<br />Config: Configuration file has the environmental variables of URL, Userid, Password, Pool...
13<br />Test Plan Structure (continued)<br />Recovery: Contains some attachments for Recovery Scenarios in .qrs(Quick Test...
14<br />Handoff and Performance Folder <br />Handoff folder:<br />Folder structure is same as the structure mentioned abov...
15<br />Script Components Guideline<br />When the script is developed and ready for execution, follow the guidelines given...
Upcoming SlideShare
Loading in...5
×

Automation Framework 042009 V2

881

Published on

Test Automation Framework

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
881
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
47
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Automation Framework 042009 V2

  1. 1. 1<br />Automation Framework<br />
  2. 2. 2<br />Test Automation Approach<br /><ul><li>The Test Script Modularity Framework
  3. 3. The Test Library Architecture Framework
  4. 4. The Keyword-Driven or Table-Driven Testing Framework
  5. 5. The Data-Driven Testing Framework
  6. 6. The Hybrid Test Automation Framework</li></li></ul><li>3<br />Test Automation Framework<br /> The most commonly implemented framework is a combination of all of the above techniques, pulling from their strengths and trying to mitigate their weaknesses. <br /> NexOS Test Automation Framework (Hybrid) =<br />Test Script Modularity / Test library Framework<br /> +<br />The DataDriven Testing Framework<br />
  7. 7. 4<br />Test Script Modularity Framework<br />The test script modularity framework requires the creation of small, independent scripts that represent modules, sections, and functions of the application-under-test.<br />These small scripts are then used in a hierarchical fashion to construct larger tests, realizing a particular test case.<br />
  8. 8. 5<br />Test Library Architecture Framework<br />The test library architecture framework is very similar to the test script modularity framework and offers the same advantages, but it divides the application-under-test into procedures and functions instead of scripts.<br />This framework requires the creation of library files (SQABasic libraries, APIs, DLLs, and such) that represent modules, sections, and functions of the application-under-test. These library files are then called directly from the test case script.<br />This is incorporated in NexOS Project by creation of Business functions which are specific to partition/workspace/reveal in vbs files and NexOS,generic / Global functions (for each web Object). which are used as libraries.<br />
  9. 9. 6<br />VBS files for Partitions<br />Partition in NexOSLibrary file<br /> 1.Login NexOS_Login.vbs <br /> 2.Application NexOS_Application.vbs<br /> 3.Credit NexOS_Credit.vbs<br /> 4.LPF NexOS_LPF.vbs<br /> 5.PRP NexOS_PRP.vbs<br /> 6.Registration NexOS_Registration.vbs<br /> 7.Underwriting NexOS_Underwriting.vbs<br /> 8.Submit NexOS_Submit.vbs<br /> 9.Pipeline NexOS_Pipeline.vbs<br /> Each .vbs file has the functions defined for that particular partition <br />
  10. 10. 7<br />VBS files for Generic Functions<br />Functionality Library File<br />1.Datatable DataTable.vbs<br /> 2.Global Global.vbs<br /> 3.Reporting HTML.vbs<br /> 4.Object Descriptions Constants.vbs<br /> 5.Messages messages.vbs<br /> 6.Utilities util.vbs<br />
  11. 11. 8<br />Data-Driven Testing Framework<br />Data-driven testing framework is incorporated in NexOS Project by inputting the data into an Excel file and importing the values into QTP Data table at the time of execution. <br />Enables to test the application with multiple sets of data.<br />
  12. 12. 9<br />Configuration Settings<br />Environment Variables (read only data) are declared in Config.ini file<br />Following are the Environment variables:<br /><ul><li>AccessResultsLocation
  13. 13. ScreenshotRootpath
  14. 14. POS_Validation
  15. 15. TakeScreenshot</li></li></ul><li>10<br />Login Configuration<br />The user id, password (encrypted) and environment (URL) and the Host Name are driven from the Login_Config.xls file attached to the config folder in the QC test plan<br />Default URL i.e., http://originationit will be taken if there is no entry for the URL and the QC User Name will be taken to login to the application if there is no userId Provided in the Login_Config.xls file<br />
  16. 16. 11<br />Folder Structure<br />Test Plan consists of three main folders:<br />Development contain scripts under construction<br />Handoff are scripts delivered to client. <br />Performance are scripts modified <br /> for stress testing.<br />Each folder structure contains:<br /> Config Documents<br /> LIB OR<br /> Recovery Scripts<br />Test Plan<br />
  17. 17. 12<br />Test Plan Structure<br />Config: Configuration file has the environmental variables of URL, Userid, Password, Pool, AccessResultsLocation path, Login config path, Screenshot root path, POS validation and Take Screen shot.<br />Documents:Documents folder contains all documents required for preparation and understanding of the NexOS Automation project.<br />LIB: Contains Business Library and Global Library Functions located in the form of vbs file<br />OR:Contains object repository files attached in the Attachment section. Object Repository is used in Login part of the application, because some win objects are not identified by the descriptive programming or takes more time to identify. The file is saved in .tsr( Test Shared Repository) extension.<br />
  18. 18. 13<br />Test Plan Structure (continued)<br />Recovery: Contains some attachments for Recovery Scenarios in .qrs(Quick Test Recovery Scenario) and .vbs files are attached in Attachment section<br />Scripts: Contains Integration and POS folders, where integration folder contains Test set folder, in Test Set Process Flow folder wise is divided, respected test scripts and the Smoke Test Cases. Each test script has its own test data attached in the attachment section. POS folder contains all the pos test scripts and the test data attached to the Attachment section.<br />The Test Scenarios in NexOS automation Project are divided into different Test Sets, each Test Set contains 10 Process Flows, each flow contains different Test scenario Scripts, for each script test data is attached in the Attachment section. <br />Test Set (X)->Process Flow (X)->Test Script<br />
  19. 19. 14<br />Handoff and Performance Folder <br />Handoff folder:<br />Folder structure is same as the structure mentioned above (i.e. Config, Documents, LIB, OR, Recovery, Results and Scripts).<br />Process of delivering the scripts is a folder is created with a date 2007_11_15(start date of deliverables). <br />Performance folder:<br />These set of scripts were to support performance testing team and returns the page rendering time.<br />
  20. 20. 15<br />Script Components Guideline<br />When the script is developed and ready for execution, follow the guidelines given below:<br /><ul><li>Connect to Quality Center.
  21. 21. Ensure that Test Data (Excel sheet) is attached to the Test Script.
  22. 22. Add all the Library files required for test execution in LIB.
  23. 23. Add Configuration file in Config folder.
  24. 24. Add Object Repository file in OR.</li></li></ul><li>16<br />Script Execution from Test Lab<br /><ul><li>Go to Test Lab in Quality Center
  25. 25. Select the required test from the execution grid and click on Run button on the header,
  26. 26. Select the required host for execution and again click on Run button in the Pop up window
  27. 27. Quality Center will initiate QTP and executes the selected script.
  28. 28. Click on Run Test Set button in order to run the entire Test set </li></li></ul><li>17<br />Execution From QualityCenter<br />
  29. 29. 18<br />Test Results<br />Test Results are of two types:<br />Reporting<br />Screen shots<br />Reporting - Test Results are stored in two places. <br />Microsoft Access (Database) <br />Test Lab in Quality Center.<br />Screen shots<br />
  30. 30. 19<br />Storing Results in Access and QC<br />Tracking Results in MS-Access:<br />All the Verification points in each script are stored in the Respective Table of the MS-Access. Results can be tracked at the following location which can be configurable from the configuration file. <br />Path : agotsnexosdev03E$NexOS.KiranNEXOSTestDataNexOSPOS.mdb<br />Test Lab in Quality Center:<br />Go to Test Lab Tab in the Quality centre<br />Double click on the script executed in the Execution grid<br />Double click on the Run Name in the Test instance Properties Dialog Box<br />Verify the results in the Run Steps Dialog box <br />
  31. 31. 20<br />QualityCenter Execution Example<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×