Automation in Software Source Code Development

Full Text (PDF, 540KB), PP.1-9

Views: 0 Downloads: 0

Author(s)

Henryk Krawczyk 1,* Dawid Zima 1

1. Department of Computer Systems Architecture, Gdansk University of Technology, Poland

* Corresponding author.

DOI: https://doi.org/10.5815/ijitcs.2016.12.01

Received: 10 Feb. 2016 / Revised: 12 Jun. 2016 / Accepted: 7 Sep. 2016 / Published: 8 Dec. 2016

Index Terms

Continuous integration, continuous delivery, continuous deployment, test automation, debug automation

Abstract

The Continuous Integration idea lays beneath almost all automation aspects of the software development process. On top of that idea are built other practices extending it: Continuous Delivery and Continuous Deployment, automating even more aspects of software development. The purpose of this paper is to describe those practices, including debug process automation, to emphasize the importance of automating not only unit tests, and to provide an example of complex automation of the web application development process.

Cite This Paper

Henryk Krawczyk, Dawid Zima, "Automation in Software Source Code Development", International Journal of Information Technology and Computer Science(IJITCS), Vol.8, No.12, pp.1-9, 2016. DOI:10.5815/ijitcs.2016.12.01

Reference

[1]Forrester Consulting, “Continuous Delivery: A Maturity Assessment Model,” 2013.

[2]D. Zima, “Modern Methods of Software Development,” TASK Quarterly, tom 19, nr 4, 2015. 

[3]M. Fowler, “Continuous Integration,” [Online]. Available: http://www.martinfowler.com/articles/continuousIntegration.html. [Accessed 3 10 2015].

[4]A. Miller, "A Hundred Days of Continuous Integration," in Agile 2008 Conference, 2008. 

[5]M. Fowler, "ContinuousDelivery," 30 May 2013. [Online]. Available: http://martinfowler.com/bliki/ContinuousDelivery.html. [Accessed 28 November 2015].

[6]J. Humble and D. Farley, "Anatomy of the Deployment Pipeline," in Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Addison-Wesley Professional, 2010, pp. 105-141.

[7]J. Humble, "Continuous Delivery vs Continuous Deployment," 13 August 2010. [Online]. Available: http://continuousdelivery.com/2010/08/continuous-delivery-vs-continuous-deployment/. [Accessed 22 November 2015].

[8]"xUnit.net," [Online]. Available: http://xunit.github.io/. [Accessed 28 November 2015].

[9]M. Fowler, "PageObject," 10 September 2013. [Online]. Available: http://martinfowler.com/bliki/PageObject.html. [Accessed 12 February 2016].

[10]“Selenium,” [Online]. Available: http://www.seleniumhq.org/. [Accessed 12 February 2016].

[11]R. Martin, “The test bus imperative: architectures that support automated acceptance testing,” IEEE Software, tom 22, nr 4, pp. 65-67, 2005. 

[12]Y. Dang, R. Wu, H. Zhang, D. Zhang and P. Nobel, "ReBucket: A Method for Clustering Duplicate Crash Reports Based on Call Stack Similarity".

[13]"Using the !analyze Extension," [Online]. Available: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560201. [Accessed 22 November 2015].

[14]K. Glerum, K. Kinshumann, S. Greenberg, G. Aul, V. Orgovan, G. Nichols, D. Grant, G. Loihle and G. Hunt, "Debugging in the (very) large: ten years of implementation and experience," in Proceedings of the ACM SIGOPS 22nd symposium on Operating systems principles, 2009.

[15]Zaigham Mushtaq, M. Rizwan Jameel Qureshi, "Novel Hybrid Model: Integrating Scrum and XP", IJITCS, vol.4, no.6, pp.39-44, 2012.