Usefulness and Effectiveness of Test-First Development and Junit Framework

Myint Myint Moe

Abstract


Test-First development (TFD) is a process that relies on the repetition of a very short development cycle. It is based on the test-first concept of extreme programming (XP) that encourages simple design with a high level of confidence. Test-First development is a software development practice where small sections of test code are used to direct the development of program units. Writing test code prior to the production code promises several positive effects on the development process itself and on associated products and processes as well. Thus, it is difficult to assess the potential process and product effects when applying test-First development. Test-First development can reduce the amount of introduced defects and lead to more maintainable code. Parts of the implemented code may also be somewhat smaller in size and complexity. While maintenance of test-First code can take less time, initial development may last longer. TFD defines a proven way to ensure effective unit testing.


Keywords


TFD, Refactoring, Duplicating, JUnit.

Full Text:

PDF

References


Viktor Farcic, Alex Garcia; Test-Driven Java Development; Invoke TDD principles for end-to-end application development with Java; Copyright © 2015 Packt Publishing; First published: August 2015; Production reference: 1240815; Published by Packet Publishing Ltd. ISBN 978-1-78398-742-9; www.packtpub.com

By David Astels; Publisher: Prentice Hall PTR; Test-Driven Development: A Practical Guide; Pub Date: July 02, 2003; ISBN: 0-13-101649-0

Jürgen Münch, Simo Makinen; “Effects of Test-Driven Development: A Comparative Analysis of Empirical Studies”; © Springer 2014; Proceedings of the 6th International Conference Software Quality Days (SWQD 2014), Vienna,Austria, January 14-16, 2014.

André A. S. Ivo1,2* , Eduardo M. Guerra2, Sandy M. Porto2, Joelma Choma2 and Marcos G. Quiles3; An approach for applying Test-Driven Development (TDD) in the development of randomized algorithms; Ivo et al. Journal of Software Engineering Research and Development (2018) 6:9; https://doi.org/s40411-018-0053-5; © The Author(s). 2018 Open Access

Roberto Latorre, “A successful application of a Test-Driven Development strategy in the industrial environment”; © Springer Science+Business Media New York 2013

Corrigan Johnson; “SPEST - A TOOL FOR SPECIFICATION-BASED TESTING”; the Faculty of California Polytechnic State University, San Luis Obispo, January 2016

Raquelita Ros Aguilar, “Using Test-Driven Development to Improve Software Development Practices”; School of Computer Science; REYKJAVIK UNIVERSITY, SPRING 2016; T-622-UROP.

Davide Fucci, Simone Romano, Maria Teresa Baldassarre; “A Longitudinal Cohort Study on the Retainment of Test-Driven Development”; ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) (ESEM ’18), October 11–12, 2018, Oulu, Finland. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/3239235.3240502

Shaweta Kumar, Sanjeev Bansal; “Comparative Study of Test Driven Development with Traditional Techniques”; International Journal of Soft Computing and Engineering (IJSCE) ISSN: 2231-2307, Volume-3, Issue-1, March 2013 352

Naomi Unkelos-Shpigel (&) and Irit Hadar; “Test First, Code Later: Educating for Test Driven Development, Teaching Case”; Information Systems Department, University of Haifa, Carmel Mountain, 31905 Haifa, Israel.




DOI: http://dx.doi.org/10.52155/ijpsat.v13.1.734

Refbacks

  • There are currently no refbacks.


Copyright (c) 2019 Myint Myint Moe

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.