• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Code coverage for automation scripts
 

Code coverage for automation scripts

on

  • 1,810 views

Challenge: As the product is a vast product that provides so regression suite of this was very big. It was taking about 14 days to execute and with every release it was increasing. The main challenge ...

Challenge: As the product is a vast product that provides so regression suite of this was very big. It was taking about 14 days to execute and with every release it was increasing. The main challenge was to keep regression suite comprehensive as well small so that it can be executed many time. Solution Emma was used to find code coverage of product code then redesign the regression suite.

Statistics

Views

Total Views
1,810
Views on SlideShare
1,810
Embed Views
0

Actions

Likes
0
Downloads
18
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Code coverage for automation scripts Code coverage for automation scripts Presentation Transcript

    • Presented By: Aakash Tyagi
    •  Background Challenge Proposed Solution Reporting Benefits Conclusion 2
    • The product was big product that provide a lot of functionality.The Product was developed in Java language.QA Team was using Rational Function Tool(RFT) for automation ofregression suite. 3
    • As the product is a vast product that provides a lot of functionality soregression suite of this was very big.It was taking about 14 days to execute and with every release it wasincreasing.Regression suite was not so efficient as it was not catching bug sofrequently.Team was unaware of the amount of code coverage achieved withautomation test suite execution and what parts of application wereexecuted and what parts were not.The main challenge was to keep regression suite comprehensive sothat it is likely to catch all the bugs introduced as well small so that itcan economically be executed many times. 4
    • EMMA tool was to be used to find out the coverage of Java basedapplications.EMMA was to be used on the server machine where the source codeof the application was executing.RFT scripts were to be executed and got the source code coveragedetails from EMMA tool.
    • InstrumentationApplication Emma Meta Data By Emma Emma API Instrumented Application Web Browser Web Server RFT Test Report Emma session data Reporting By Coverage ReportEmma Meta Data Emma 6
    • DEMO
    •  Emma produce report in HTML format that contain what % of classes, blocks and lines were executed.eg Emma also provide help to identify the code which were executed and which were not by showing these in different color.eg. for unexecuted code: 8
    • Benefits Depending on the coverage results, The selected test cases can be approach provide a added to increase good input to modify code coverage and test script as we can be eliminated know what code we that are not are executing and necessary. what not. It provide input to development team to find if there is code that is no more associated with any requirement (Dead code).This code can be eliminated to reduce effort spend in management this of code.
    • Conclusion Emma can be used to know the coverage of both Manual and Automation test suite. Emma can be used with both windows and web base applications. We can use Emma with any Functional Testing Tool to find the coverage of . the automation test suite
    • Thank You