Highly Automated Agile Testing Process: An Industrial Case Study

• Autorzy: Berłowski J. , Chruściel P. , Kasprzyk M. , Konaniec I. , Jureczko M.

Identyfikatory

DOI

10.5277/e-Inf160104

• Języki publikacji: EN

Abstrakty

EN

This paper presents a description of an agile testing process in a medium size software project that is developed using Scrum. The research methods used is the case study were as follows: surveys, quantifiable project data sources and qualitative project members opinions were used for data collection. Challenges related to the testing process regarding a complex project environment and unscheduled releases were identified. Based on the obtained results, we concluded that the described approach addresses well the aforementioned issues. Therefore, recommendations were made with regard to the employed principles of agility, specifically: continuous integration, responding to change, test automation and test driven development. Furthermore, an efficient testing environment that combines a number of test frameworks (e.g. JUnit, Selenium, Jersey Test) with custom-developed simulators is presented.

Słowa kluczowe

EN

software engineering; testing process; agile software development; case study

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2016
• Tom: Vol. 10, nr 1
• Strony: 69--87
• Opis fizyczny: Bibliogr. 29 poz., tab., rys.

Twórcy

autor

Berłowski J.

• NetworkedAssets Sp. z o. o.

autor

Chruściel P.

• NetworkedAssets Sp. z o. o.

autor

Kasprzyk M.

• NetworkedAssets Sp. z o. o.

autor

Konaniec I.

• NetworkedAssets Sp. z o. o.

autor

Jureczko M.

• Faculty of Computer Science and Management, Wrocław University of Science and Technology

Bibliografia

• [1] A. Bertolino, “Software testing research: Achievements, challenges, dreams,” in Future of Software Engineering, FOSE ’07. IEEE, 2007, pp. 85–103.
• [2] V. Kettunen, J. Kasurinen, O. Taipale, and K. Smolander, “A study on agility and testing processes in software organizations,” in Proceedings of the 19th international symposium on Software testing and analysis. ACM, 2010, pp. 231–240.
• [3] K. Beck and C. Andres, Extreme programming explained: embrace change. Addison–Wesley Professional, 2004.
• [4] L. Koskela, Test driven: practical TDD and ac- ceptance TDD for Java developers. Manning Publications Co., 2007.
• [5] M. Jureczko, “The level of agility in the testing process in a large scale financial software project,” in Software engineering techniques in progress, T. Hruška, L. Madeyski, and M. Ochodek, Eds. Oficyna Wydawnicza Politechniki Wrocławskiej, 2008, pp. 139–152.
• [6] D. Talby, A. Keren, O. Hazzan, and Y. Dubinsky, “Agile software testing in a large-scale project,” IEEE Software, Vol. 23, No. 4, 2006, pp. 30–37.
• [7] K. Karhu, T. Repo, O. Taipale, and K. Smolander, “Empirical observations on software test- ing automation,” in International Conference on Software Testing Verification and Validation, ICST ’09. IEEE, 2009, pp. 201–209.
• [8] K. Schwaber, Agile project management with Scrum. Microsoft Press, 2004.
• [9] P. Runeson and M. Höst, “Guidelines for con-ducting and reporting case study research in software engineering,” Empirical Software Engineering, Vol. 14, No. 2, 2009, pp. 131–164.
• [10] R. Mall, Fundamentals of software engineering. PHI Learning Pvt. Ltd., 2009.
• [11] K. Petersen and C. Wohlin, “Context in industrial software engineering research,” in Proceedings of the 3rd International Symposium on Empirical Software Engineering and Measurement. IEEE Computer Society, 2009, pp. 401–404.
• [12] S. Harichandan, N. Panda, and A.A. Acharya, “Scrum testing with backlog management in agile development environment,” International Journal of Computer Science and Engineering, Vol. 2, No. 3, 2014.
• [13] K.K. Jogu and K.N. Reddy, “Moving towards agile testing strategies,” CVR Journal of Science & Technology, Vol. 5, 2013.
• [14] M. Puleio, “How not to do agile testing,” in Agile Conference. IEEE, 2006, pp. 305–314.
• [15] K. Beck, Test driven development: By example. Addison–Wesley Professional, 2003.
• [16] M. Jureczko and M. Mlynarski, “Automated acceptance testing tools for web applications using test-driven development,” Electrical Review, Vol. 86, No. 09, 2010, pp. 198–202.
• [17] S. Ambler, Agile modeling: effective practices for extreme programming and the unified process. Wiley, 2002.
• [18] C. Kaner, J. Bach, and B. Pettichord, Lessons learned in software testing. John Wiley & Sons, 2008.
• [19] D. Martin, J. Rooksby, M. Rouncefield, and I. Sommerville, “ ‘Good’ organisational reasons for ’bad’ software testing: An ethnographic study of testing in a small software company,” in 29th International Conference on Software Engineering, ICSE 2007. IEEE, 2007, pp. 602–611.
• [20] M. Catelani, L. Ciani, V.L. Scarano, and A. Bacioccola, “Software automated testing: A solution to maximize the test plan coverage and to increase software reliability and quality in use,” Computer Standards & Interfaces, Vol. 33, No. 2, 2011, pp. 152–158.
• [21] R. Löffler, B. Güldali, and S. Geisen, “Towards model-based acceptance testing for Scrum,” Softwaretechnik-Trends, Vol. 30, No. 3, 2010.
• [22] X. Wang and P. Xu, “Build an auto testing frame- work based on selenium and fitnesse,” in Inter- national Conference on Information Technology and Computer Science, ITCS 2009, Vol. 2. IEEE, 2009, pp. 436–439.
• [23] T. Xie, “Improving effectiveness of automated software testing in the absence of specifications,” in 22nd IEEE International Conf. on Software Maintenance, ICSM ’06. IEEE, 2006, pp. 355–359.
• [24] N. Nagappan, E.M. Maximilien, T. Bhat, and L. Williams, “Realizing quality improvement through test driven development: results and experiences of four industrial teams,” Empirical Software Engineering, Vol. 13, No. 3, 2008, pp. 289–302.
• [25] A.P. Ress, R. de Oliveira Moraes, and M.S. Salerno, “Test-driven development as an innova- tion value chain,” Journal of technology manage- ment & innovation, Vol. 8, 2013, p. 10.
• [26] L. Madeyski, “The impact of pair programming and test-driven development on package depen- dencies in object-oriented design—an experiment,” in Product-Focused Software Process Improvement. Springer, 2006, pp. 278–289.
• [27] L. Madeyski, “The impact of test-first programming on branch coverage and mutation score indicator of unit tests: An experiment,” Information and Software Technology, Vol. 52, No. 2, 2010, pp. 169–184.
• [28] J. Winter, K. Rönkkö, M. Ahlberg, and J. Hotchkiss, “Meeting organisational needs and quality assurance through balancing agile and formal usability testing results,” in Soft- ware Engineering Techniques. Springer, 2011, pp. 275–289.
• [29] Y. Dubinsky, D. Talby, O. Hazzan, and A. Keren, “Agile metrics at the Israeli air force,” in Agile Conference, Proceedings. IEEE, 2005, pp. 12–19.