Advertisement

Unit Testing in Global Software Development Environment

  • Sanjay MisraEmail author
  • Adewole Adewumi
  • Rytis Maskeliūnas
  • Robertas Damaševičius
  • Ferid Cafer
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 799)

Abstract

Global software development has many challenges. Amongst them maintaining quality in the code developed in distributed sites is also a challenge. One of effective way to control the quality of the code is the unit testing. It removes defects at the early stage of development and further reduces the testing and maintenance efforts at the later phase of the development lifecycle. In this paper, a class complexity metric for testing the class, which is normally treated as a unit in object-oriented programming is proposed. The applicability of class complexity metrics for unit testing is demonstrated through a project in JAVA.

Keywords

Global software development Unit testing Software metrics 

Notes

Acknowledgements

We acknowledge the support and sponsorship provided by Covenant University through the Centre for Research, Innovation and Discovery (CUCRID).

References

  1. 1.
    Cammarano, B.: Geographically distributed development with the IBM software development platform: a unified life cycle approach. In: Global Communication, Global Development, Global Success, Rational Software IBM, pp. 1–19 (2004)Google Scholar
  2. 2.
    Anschuetz, L.: Managing geographically distributed team. In: Proceedings of the IEEE IPCC 1998, pp. 1–10 (1998)Google Scholar
  3. 3.
    Ambler, S.W.: Agile strategies for geographically distributed quality management. Agile J. 1–4 (2007)Google Scholar
  4. 4.
    Richardson, I., Casey, V., Zage, D., Zage, W.: Global Software development – the challenges (2004). www.serc.net/report/tr278.pdf
  5. 5.
    Wade, K.: Successfully managing geographically distributed development. In: Rational Software IBM, pp. 1–12, August 2004Google Scholar
  6. 6.
    Boehm, B.: Software Engineering Economics. Prentice Hall, Englewood Cliffs (1981)zbMATHGoogle Scholar
  7. 7.
    Misra, S., Akman, I.: Weighted class complexity: a measure of complexity for object-oriented system. J. Inf. Sci. Eng. 24, 1689–1708 (2008)Google Scholar
  8. 8.
    Costagliola, G., Tortora, G.: Class points: an approach for the size estimation of object-oriented systems. IEEE Trans. Soft. Eng. 31, 52–74 (2005)CrossRefGoogle Scholar
  9. 9.
    Chidamber, S.R., Kermer, C.F.: A metric suite for object oriented design. IEEE Trans. Softw. Eng. 20(6), 476–493 (1994)CrossRefGoogle Scholar
  10. 10.
    Kim, K., Shin, Y., Wu, C.: Complexity measures for object-oriented program based on the entropy. In: Proceedings of APSEC, pp. 127–136 (1995)Google Scholar
  11. 11.
    Binder, R.V.: Object-oriented software testing. CACM 37(9), 29 (1994)Google Scholar
  12. 12.
    Basily, V.R., Briand, L.C., Melo, W.L.: A validation of object oriented design metrics as quality indicators. IEEE Trans. Softw. Eng. 22(1), 751–761 (1996)CrossRefGoogle Scholar
  13. 13.
    Misra, S.: A metric for global software development environments. Proc. Indian Nat. Sci. Acad. 75(4), 145–158 (2009)Google Scholar
  14. 14.
    Wang, Y., Shao, J.: A new measure of software complexity based on cognitive weights. Can. J. Electr. Comput. Eng. 28(2), 69–74 (2003)CrossRefGoogle Scholar
  15. 15.
  16. 16.
    Weyuker, E.: Evaluating software complexity measures. IEEE Trans. Softw. Eng. 14, 1357–1365 (1988)MathSciNetCrossRefGoogle Scholar
  17. 17.
    Briand, L.C., Morasca, S., Basily, V.R.: Property based software engineering measurement. IEEE Trans. Softw. Eng. 22, 68–86 (1996)CrossRefGoogle Scholar
  18. 18.
    Kaner, C.: Software engineering metrics: what do they measure and how do we know? In: Proceedings of 10th International Software Metrics Symposium, Metrics (2004)Google Scholar
  19. 19.
    McCabe, T.J.: A complexity measure. IEEE Trans. Softw. Eng. 2(6), 308–320 (1976)MathSciNetCrossRefGoogle Scholar
  20. 20.
    Halstead, M.H.: Elements of Software Science. Elsevier North-Holland, New York (1997)zbMATHGoogle Scholar
  21. 21.
    Mackinnon, T., Freeman, S., Craig, P.: Endo-testing: unit testing with mock objects. In: Succi, G., Marchesi, M. (eds.) Extreme Programming Examined, pp. 287–302. Addison Wesley Longman, Reading (2001). chapter 17Google Scholar
  22. 22.
    Cheon, Y., Leavens, Gary T.: A simple and practical approach to unit testing: the JML and JUnit way. In: Magnusson, B. (ed.) ECOOP 2002. LNCS, vol. 2374, pp. 231–255. Springer, Heidelberg (2002).  https://doi.org/10.1007/3-540-47993-7_10CrossRefGoogle Scholar
  23. 23.
    Link, J., Fröhlich, P.: Unit testing in Java: how tests drive the code. Morgan Kaufmann, Los Altos (2003)CrossRefGoogle Scholar
  24. 24.
    Fiedler, S.P.: Object-oriented unit testing-HP’s Waltham div-technical, pp. 69–74. Hewlett-Packard J. (1989)Google Scholar
  25. 25.
    Hunt, A., Thomos, D, Hargett, M.: Pragematic unit test in C# with NUnit. The PragmaticBookself, USA. ISBN-13 978-0-9776166-7-4Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2018

Authors and Affiliations

  • Sanjay Misra
    • 1
    Email author
  • Adewole Adewumi
    • 1
  • Rytis Maskeliūnas
    • 2
  • Robertas Damaševičius
    • 2
  • Ferid Cafer
    • 3
  1. 1.Covenant UniversityOtaNigeria
  2. 2.Kaunas University of TechnologyKaunasLithuania
  3. 3.TurkcellIstanbulTurkey

Personalised recommendations