Automated Test Execution & Reporting (TER) Plugin using JIRA Banani Ghosh, Software Engineer Tanvi Dharmarha, Quality Engineering Manager Adobe Systems Logo of your organization

Abstract

Automated Testing Life Cycle

Problem in Automated Testing Major focus Building the Framework Develop scripts to automate workflows Little or No Attention Managing Automation Test runs for each build Efficient Updation of execution Results Result loss of tracking testing activity makes automation efforts somewhat redundant Automated Frameworks created Across several projects across various companies Unavailability of open source Test case Execution & Reporting Plugin in JIRA Increases time of building Automation frameworks

JIRA Overview Tracking tool for: Issue & Tests task web-based tool extensible platform An extensible platform allowing customizable items to match the business purposes developed by Atlassian for project management

Zephyr Overview On-demand Enterprise Test Management Platform Easy management of the following : Test resources Manual Test Cases Link to Automation Scripts Defect Tracking

Zephyr for JIRA

Zephyr for JIRA

Core System Features Connects Fetches test details for JIRA Host Automation framework Fetches test details for - Project id - Version id Create Test Execution Cycles : New OR Cloned Add test sets to cycle Mapping Done Execution IDs ::: Test case keys Parallel Execution Updates test cases in JIRA

System Architecture

Testcase Generator Module

Testcase Updater Module

Results All relevant information available at anytime in the execution History

Results Contd…

Results Contd… Daily Results available on JIRA Dashboard This is NOT possible when Reports shared over mail

Time with 3rd Party tools Time with 3rd Party tools Results Contd… 3rd Party Reporting tools vs TER Plugin Integrate & get accustomed to use and debug Time with 3rd Party tools Time with TER Plugin 3 - 4 weeks < 1 day Development Time after Integration Time with 3rd Party tools Time with TER Plugin ~ 12 - 15 days < 3 days Reduced Cost of Development

Learnings Communication between Jira and Zephyr Rest APIs Internal Mapping of Projects, Versions and Issues in Jira Architecture of Test case management fields in Jira Building RESTful Web services using JAX-RS Synchronization and Deadlock handling to ensure parallelism

Key TakeAways Automation is imperative but Reporting is Key Seamless integration with minimal code and configuration Pluggable and Extensible

References & Appendix [1]http://www.seleniumhq.org/ [2]http://watir.com/ [3]https://www.getzephyr.com/products/zephyr-for-jira [4]https://en.wikipedia.org/wiki/Producer%E2%80%93consumer_pro blem

Author Biography Tanvi Dharmarha is working with Adobe Systems as Quality Engineering Manager and has over 10 years of experience in manual, automated and API testing. She owns the quality engineering for Adobe Crash Reporting System. Tanvi has several paper publications to her credit. She holds an engineering degree in Information Technology and is also a certified Stanford Advanced Project Manager. Banani Ghosh is working with Adobe Systems as Senior Software Engineer having 2years of experience in manual, automated and API Testing. She has been working as a quality engineer for Adobe Crash Reporting System. She holds an engineering degree in Electronics and Electrical. Prior to Adobe she has worked with Aricent Technologies in Telecom domain being responsible in developing and maintaining several Security Gateway APIs and tools.

Logo of your organization Thank You!!! Logo of your organization