Your SlideShare is downloading. ×
0
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
How to Build an In-House Common Test Automation Platform
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

How to Build an In-House Common Test Automation Platform

1,624

Published on

This presentation is meant for giving a high level overview of my submission of the topic to an upcoming test automation conference.

This presentation is meant for giving a high level overview of my submission of the topic to an upcoming test automation conference.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,624
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How to Build an In-House<br />Common Test Automation Platform<br />Success Story of on object-oriented Python/C++ framework <br />Rahul Verma<br />rahul_verma@mcafee.com<br />rahul_verma@testingperspective.com<br />Sr QA Technical Lead,<br />Anti-Malware Core,<br />McAfee Labs<br />
  • 2. Speaker Profile<br />Rahul Verma is a Sr QA Technical Lead with McAfee Software India, with special interest in performance testing, security testing, Python and design of test automation frameworks. Rahul has presented at several conferences, organizations and academic institutions including CONQUEST, STeP-IN, ISQT,  TEST2008, Yahoo! India, McAfee, Applabs, IIT Chennai and STIG. <br />He runs the website – Testing Perspective (www.testingperspective.com ) for which he got the Testing Thought Leadership Award. His paper on the subject of “Design of Fuzzing Frameworks” won the “Best Innovative Paper “Award at TEST2008. He also recently launched a website Testing in Python (http://testinginpython.appspot.com ) powered by Google AppEngine<br />
  • 3. Test Management system – High Level Snapshot<br />Testing Non-AMCore Products<br />Testing AMCore<br /><ul><li>Any Product
  • 4. Any Tool(s)
  • 5. Any Language
  • 6. Unit Tests
  • 7. API Tests
  • 8. Black –Box Tests</li></ul>Python/C++<br />Django<br />SQLite<br />Matplotlib<br />
  • 9. Unit Tests<br /><ul><li>C/C++
  • 10. Use: </li></ul>AMCore White-box and Test Double (DLL Mocking) Library<br /> OR<br /> CPPUnitLite framework<br /><ul><li> BullsEye Coverage for tests measured against – “Unit Tests Code Coverage”</li></ul>Component Tests<br /><ul><li>C/C++
  • 11. Use: </li></ul>AMCore White-box and Test Double (DLL Mocking) Library<br />- BullsEye Coverage for tests measured against – “Component Tests Code Coverage”<br />AMCore-TMS<br />System Tests<br /><ul><li> Python/Perl/AutoIt
  • 12. Use: </li></ul>AMCore Python Utilities Library<br />- BullsEye Coverage for tests measured against – “System Tests Code Coverage”<br />Non-Functional Tests<br /><ul><li>Python/Perl/AutoIt
  • 13. Use: </li></ul>AMCore Python Utilities Library<br />- Include performance and fuzzing tests<br />Python Library<br />All of these use the underlying Python library for <br />Scheduling/Running/Script Generation and Reporting<br />
  • 14. Framework is based on <br />“Test encapsulation”<br />There are a lot of things a test would like to KNOW for itself at run time…<br />
  • 15. Framework is based on <br />“Test encapsulation”<br />There are a lot of things a test would like to DO at run time…<br />
  • 16. The properties and methods discussed in the previous slides are common across most tests but their values/implementation would vary for different tests.<br />Framework should support:<br /><ul><li> Populating test properties provided as constants e.g. Test Author / Creation Date etc.
  • 17. Populating test properties that are known at run time e.g. Platform under test
  • 18. Execute the Test API in the expected sequence. E.g.</li></ul>Test.prepare()<br />Test.setup()<br />Test.run()<br />Test.report()<br />Test.teardown()<br />via the framework.<br />Test Encapsulation – “How?”<br />
  • 19. Notes on Key Aspects of AMCore-TMS<br />Built on top of a general purpose object-oriented library<br />Has library to support DLL Mocking as well as the white box test library<br />Runs in three modes – Offline/Runner/Controller<br />Supports offline development with Script generation<br />Pickling is employed for configurations/results/interface state management<br />Tests are scheduled for a given “platform-label” and not a particular machine IP or name.<br />For each platform-label there could be multiple runner machines configured and a machine could belong to multiple platform-labels<br />Runner names are logical and do not map to the actual machine name. So, is the platform of a given runner name.<br />
  • 20. Notes on AMCore-TMS<br />Groups tests into Test-Group, Test Sub-Group, Type (Black-box/whitebox) and Test Category.<br />Class names and purpose map to the testing theory – Test Category, Test, TestOracle, TestResults, TestRunner etc.<br />All information that is required to run a test is contained in a test – via properties<br />Any run-time errors in a test are confined to the test and does not stop execution.<br />Reports detailed information for a test category right to the level of timestamp, oracle, actual result, employed tool etc. for an individual check<br />
  • 21. Notes on AMCore-TMS<br />Employs Pull Model of execution – a runner machine pulls execution details by sending a single parameter i.e. its name (logical)<br />State of execution of a runner machine is maintained on the controller machine so that tests are managed across multiple restarts or even fresh snapshots.<br />Apache web server is used as the controller side multi-threaded daemon. So, no socket programming involved.<br />Runners use HTTP protocol to pull execution settings, intermittent reporting of status and fetching state information<br />Status of execution for current or past test cycles can be seen in the web interface<br />Easy archiving because everything is file based including the DB.<br />
  • 22. AMcore-TMS – What it employs<br />Programming:<br />Python 2.5 (controller)/2.6(test nodes) as the base language<br />C/C++ for white-box lib (utilities and test doubles)<br />AutoIt for behavior generation<br />Apache web server (2.2) + mod_python<br />SQLite as the database (file based)<br />Following Python modules are used:<br />Django for Web interface (based on MVC design pattern)<br />Matplotlib for plotting test cycle status and performance statistics<br />API-documentation for the package is done using epydoc<br />WMI is used for performance stats logging<br />Urllib2 for http communication<br />
  • 23. Q/A<br />I hear and I forget. I see and I remember. I do and I understand. - Confucious <br />

×