Pipeline Orchestration for Test Automation using Extended Buildbot Architecture

Print
 
Download Full Text
IJCA Proceedings on Emerging Applications of Electronics System, Signal Processing and Computing Technologies
© 2015 by IJCA Journal
NCESC 2015 - Number 1
Year of Publication: 2015
Authors:
Sushant G. Gaikwad
M. A. Shah

Sushant G.gaikwad and M.a.shah. Article: Pipeline Orchestration for Test Automation using Extended Buildbot Architecture. IJCA Proceedings on Emerging Applications of Electronics System, Signal Processing and Computing Technologies NCESC 2015(1):21-25, September 2015. Full text available. BibTeX

@article{key:article,
	author = {Sushant G.gaikwad and and M.a.shah},
	title = {Article: Pipeline Orchestration for Test Automation using Extended Buildbot Architecture},
	journal = {IJCA Proceedings on Emerging Applications of Electronics System, Signal Processing and Computing Technologies},
	year = {2015},
	volume = {NCESC 2015},
	number = {1},
	pages = {21-25},
	month = {September},
	note = {Full text available}
}

Abstract

Whenever developers do any changes into code base of software, they want to see effect of changes quickly, Continuous Integration can solve this problem. In recent software development where agile methodology is followed turnaround time for software is less, this leads to availability of less time to develop, build and test processes. Test Orchestration methodology can be used to reduce testing efforts and time. Test Orchestration in broad sense is a tests execution step by step in automated fashion, where different type of tests will executes like Junit tests, Integration tests, Sniff tests, Acceptance tests and so on. Here tests are selected dynamically based on developer's check-ins. For Junit tests, we have extended Buildbot architecture which is a master/slave architecture, with a single central server and multiple build slaves. The objective of this paper is to develop distributed architecture for test orchestration. All higher level tests like functional tests, sniff tests and performance tests will execute in pipeline, finally result of all tests will send to developer through email.

References

  • P. P. Bhanu Prakash Gopularam, Yogeesha C B, "Highly scalable model for test execution in cloud environment," 18th Annual International Conference on Advanced Computing and communication, 2012.
  • The architecture of open source applications," osabook. org/en/integration. html, August 2014.
  • J. Humble and D. Farley, "Continuous delivery: reliable software releases through build, test, and deployment automation," Addison-Wesley.
  • "http://continuousdelivery. com/," August 2014.
  • http://in. wikipedia. org/wiki/continuousintegration," August 2014
  • http://www. ibm. com/developerworks/rational/library/contiuous-integration-agiledevelopment/," August 2014.
  • http://martinfowler. com/articles/continuousintegration. htm" #building a feature with continuous integration, August 2014.
  • M. Krishnan, "Software release management: a business
  • perspective" center for Advances studies on collaborative research, June 1994. M. J. A Lahtela, "Challenges and problems in release management process: A case study," IEEE 2nd International Conference on Software Engineering and Service Science (ICSESS), 2011.
  • Continuous Delivery with Jenkins – Deliver Software more quickly with Jenkins Workflow by "ClodBees Enterprise".
  • http://www. cloudsidekick. com/blog/pipelineorchestration- frameworks-part-two. html.