Status of Developers’ Testing Process
Gudrun Jeppesen, Mira Kajko-Mattsson, Jason Murphy
DOI: 10.4236/iim.2010.26042   PDF    HTML     4,282 Downloads   7,502 Views  


Even if recent methodologies bring more recognition to developers’ testing process, we still have little insight into its status within the industry. In this paper, we study the status of developers’ testing process at Nomadic Software. Our results show that the process is not uniformly executed. The company suffers from lack of control over the methods used, lack of formal communication on requirements, lack of static testing practice, and lack of testing process documentation.

Share and Cite:

Jeppesen, G. , Kajko-Mattsson, M. and Murphy, J. (2010) Status of Developers’ Testing Process. Intelligent Information Management, 2, 343-353. doi: 10.4236/iim.2010.26042.

Conflicts of Interest

The authors declare no conflicts of interest.


[1] J. W. Cangussu, R. A. DeCarlo and A. P. Mathur, “A Formel Model of the Software Test Process,” IEEE Transactions on Software Engineering, Vol. 28, No. 8, 2002, pp. 782-796.
[2] L. Groves, R. Nickson, G. Reeves, S. Revves and M. Utting, “A Survey of Software Pratices in the New Zeeland Software Industry,” Proceedings of Australian Software Engineering Conference, Queensland, 28-29 April 2000, pp. 189-201.
[3] S. P. Ng, T. Murnane, K. Reed, D. Grant and T. Y. Chen, “A Preliminary Survey on Software Practices in Australia,” Proceedings of Australian Software Engineering Conference, Melbourne, 13-16 April 2004, pp. 116-125.
[4] “Agile Software Development,” 2009. http://en.wikipedia. org/wiki/Agile_software_development
[5] H. Gallis, E. Arisholm and T. Dyka, “An Initial Framwork for Research on Pair Programming,” Proceedings of ISESE International Symposium on Empirical Software Engineering, Rome, 30 September-1 October 2003, pp. 132-142.
[6] E. M. Guerra and C. T. Fernandes, “Refactoring Test Code Safely,” Proceedings of ICSEA International Conference on Software Engineering Advances, Cap Esterel, 25-31 August 2007, p. 44.
[7] P. J. Schroeder and D. Rothe, “Teaching Unit Testing using Test-Driven Development,” 2005. http://www.testing
[8] S. Koroorian and M. Kajko-Matsson, “A Tale of Two Daily Build Projects,” Proceedings of International Conference on Software Engineering Advances, Porto, 20-25 September 2009, pp. 245-251.
[9] G. J. Meyers, T. Badgett, T. M. Thomas and C. Snadler, “The Art of Software Testing,” 2nd Edition, John Wiley & Sons, Inc., Hoboken, 2004.
[10] M. Kajko-Mattsson and T. Björnsson, “Outlining Developer’s Testing Mode,” Proceedings of EUROMICRO Conference on Software Engineering and Advanced Applications, Lübeck, 27-31 August 2007, pp. 263-270.
[11] B. Henderson-Sellers, G. Collins and I. Graham, “UML- Compatible Process,” Proceedings of 34th Annual Hawaii International Conference on System Sciences, Maui, Vol. 3, 3-6 January 2001, p. 3050.
[12] “ITM Process (IT-Product Maintenance Process),” Internal Documentation at Nomadic Software, 2009.
[13] R. Juric, “Extreme Programming and its Development Practices,” Proceedings of 22nd ITI International Conference Information Technology Interfaces, Pula, 13-16 June 2000, pp. 97-104.
[14] L. Rising and N. S. Janoff, “The Scrum Development Process for Small Teams,” 2000. risingl1/Articles/IEEEScrum.pdf
[15] M. Kajko-Matsson, “Corrective Maintenance Maturity Model: Problem Management,” Ph.D. Dissertation, Stockholm University and Royal Institute of Technology, Stockholm, 2001.
[16] M. Kajko-Mattsson, “Common Concept Apparatus within Corrective Software Maintenance,” Proceedings of International Conference on Software Maintenance, Los Alamitos, 30 August-3 September 1999, pp. 287-297.

Copyright © 2024 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.