Test-Driven Development

Present business world competition between the companies is increasing a lot with respect to quality, services and trust worthiness. Test driven development approach is one of the key factors for quality delivery of products. Test driven approach is one of amongst best practices in software from past decades. One of the most time consuming and costly processes of the Software Development Life Cycle has been the maintenance of production code. As of 2000, the overall maintenance costs have been more than 90%. To overcome this challenge many tools, frameworks and software paradigms have risen. On the forefront of this effort is writing unit test cases by the developers under the banner of Test Driven Development. This practice tackles the problem in the development phase. This work discus on TDD an issue that tackles to reduced cost and defect.

More than 50% of software development effort is spent in testing phase in a typical software development project. Test case design as well as execution consume a lot of time. Hence, automated generation of test cases is highly required. Here a novel testing methodology is being presented to test object-oriented software based on UML state chart diagrams. In this approach, function minimization technique is being applied and generate test cases automatically from UML state chart diagrams. Software testing forms an integral part of the software development life cycle. Since the objective of testing is to ensure the conformity of an application to its specification, a test "oracle" is needed to determine whether a given test case exposes a fault or not. An automated oracle to support the activities of human testers can reduce the actual cost of the testing process and the related maintenance costs. In this paper, a new concept is being presented using an UML state chart diagram and tables for the test case generation, artificial neural network as an optimization tool for reducing the redundancy in the test case generated using the genetic algorithm. A neural network is trained by the back-propagation algorithm on a set of test cases applied to the original version of the system.

Resumen Test Driven Development (Desarrollo Dirigido por Pruebas) es una disciplina de diseño y programación, donde cada nueva línea de código que escribe un programador es en respuesta a una prueba que ha fallado, también escrita por el programador. Sin ser definida como una metodología de pruebas se apoya fuertemente en las pruebas unitarias y también en pruebas de aceptación, basándose en prácticas formalizadas por Extreme Programming. Ha despertado gran interés tanto en ámbitos académicos como de la industria, encontrándose en la literatura investigaciones sobre su aplicación, aunque aún en limitado número, ya sea mediante experimentos controlados o reportes acerca de su práctica en la industria. En el presente artículo se abordará Test Driven Development en general, el dominio de su aplicación y se analizarán ventajas y desventajas de su adopción.

— Optimizing processes in software development are becoming increasingly more popular. For that reason, the consuming market demands more efficiency and quality. To achieve that, some methodologies are adopted in order to ensure that real value will be delivered to the customer. This paper relates a series of good practices based on team management features described in Scrum, and the development and source code testing covered in the TDD methodology. By specifying a framework structure with such features, this work allows software factories use a lean model, facing the reality of their projects in several aspects (e.g., team management, code development and testing).

Mock object frameworks are very useful for creating unit tests. However, purely compiled languages lack robust frameworks for mock objects. The frameworks that do exist rely on inheritance, compiler directives, or linker manipulation. Such techniques limit the applicability of the existing frameworks, especially when dealing with legacy code. We present a tool, StaticMock, for creating mock objects in compiled languages. This tool uses source-to-source compilation together with Aspect Oriented Programming to deliver a unique solution that does not rely on the previous, commonly used techniques. We evaluate the compile-time and run-time overhead incurred by this tool, and we demonstrate the effectiveness of the tool by showing that it can be applied to new and existing code.

The outline which follows analyses the two halves of a language teacher’s profession:

a) The first half is daily classroom practice : what is taught and how is it evaluated?

b) The second half of a teacher’s profession is to know or at least estimate what is going on in the brains of her students : what is learned and how is it learned?

Teaching is a simulation machine. Learning is for life. The implicit professional challenge is in making the simulation useful for living.