测试驱动开发探究

测试驱动开发是与传统程序开发方式相反的一种新型程序设计方法.它以测试编码来推动程序设计,大大缩减了设计和编码的冗余度.介绍了测试驱动开发基本思想、本质,并对测试驱动开发过程给出了清晰的流程,总结了测试驱动开发的优点.     

Professionalism and Test-Driven Development

Test-driven development is a discipline that helps professional software developers ship clean, flexible code that works, on time. In this article, the author discusses how test-driven development can help software developers achieve a higher degree of professionalism     

测试驱动开发探究

测试驱动开发是与传统程序开发方式相反的一种新型程序设计方法。它以测试编码来推动程序设计,大大缩减了设计和编码的冗余度。介绍了测试驱动开发基本思想、本质,并对测试驱动开发过程给出了清晰的流程,总结了测试驱动开发的优点。     

测试驱动开发探讨

测试驱动开发是一种新的软件开发方式。探讨了测试驱动开发方法对于软件开发的各个阶段的影响,并探讨了测试驱动开发方法的优点及其存在的问题。测试驱动开发能够提高代码的质量,帮助设计出可重用和可测试性的代码,是一个有影响的研究方向。     

Test-Driven Development of Relational Databases

In test-first development, developers formulate and implement a detailed design iteratively, one test at a time. Test-driven development (also called test-driven design) combines TFD with refactoring, wherein developers make small changes (refactorings) to improve code design without changing the code's semantics. When developers decide to use TDD to implement a new feature, they must first ask whether the current design is the easiest possible design to enable the feature's addition. Implementing test-driven database design involves database refactoring, regression testing, and continuous integration. TDDD is an integrated part of the overall development process, not a standalone activity that data professionals perform in parallel with application TDD. Although from a technical view point, TDDD is relatively straightforward, we must overcome several challenges to its whole sale adoption throughout the IT community     

Learning Test-Driven Development by Counting Lines

During the last two years, Nokia Networks has started changing much of its product development from a traditional waterfall approach to Scrum, an agile software development process. Besides Scrum, there has been a lot of focus on engineering practices such as test-driven development. We've been involved in creating TDD training at Nokia Networks to support the transition to agile development. This training approach has students write tests that count lines of code. The problems they encounter provide valuable insights into TDD and its benefits     

Incorporating Performance Testing in Test-Driven Development

Our performance-testing approach required manually inspecting the performance logs. During the project's development, JUnit-based performance testing tools, such as JUnitPerf, weren't available. Such tools provide better visibility of performance problems than manual inspection of performance logs. Although we believe manual inspection of performance trends is necessary, specifying the bottom-line performance in assert-based test cases can complement the use of performance log files, making the TFP testing results more visible to the developers. We're investigating the design of assert-based performance testing to improve the TFP process. Another direction of future work is automatic performance test generation. In this project, we relied on the performance architect's experience to identify the execution paths and measurement points for performance testing. We can derive this crucial information for performance testing from the performance requirements and system design. We plan to find guidelines for specifications of performance requirements and system design to make the automation possible     

Using Test-Driven Software Development Tools

Test Driven Development: A Practical Guide by David AstelsAgile & Iterative Development: A Manager's Guide by Craig LarmanSoftware by Numbers: Low-Risk, High-Return Development by Mark Denne and Jane Cleland-Huang     

Test-Driven Development for Spreadsheet Risk Management

Spreadsheet technology is central to the functioning of the financial sector, but professionally created spreadsheets have a high level of error, which highlights the need for innovative supporting processes and tools. The current global financial crisis will likely accelerate this need because anticipated regulation will require novel, innovative risk management methods and technologies that cover development, risk assessment, review, and other spreadsheet activities. These methods will need to be easy to understand and use and will have to serve multiple stakeholders' needs. Test-driven spreadsheet development (TDSD) is one such method. TDSD provides an ideal fit with existing market-leading spreadsheet management processes and can assist managers and auditors in the assessment and control of spreadsheet risk.     

测试驱动开发中的单元测试

在测试驱动开发中有许多种测试,单元测试只是其中的一种。本文介绍了在．NET框架下利用Nunit工具实现单元测试,并给出了一个具体的例子,其中Ibatis提供数据访问层。     

Test-Driven Development of a PID Controller

The development of embedded control systems in Simulink usually continues with automatic code generation, the build process, and several tests: software-in-the-loop (SiL), hardware-in-the-loop (HiL), and system tests in the real environment of the controller, the vehicle. Our test-driven control-system design cycle integrates into this process because it doesn't interrupt the system's model-based architecture. Furthermore, the next development cycle usually considers the results of SiL, HiL, or the system tests. With TDD, such changes cause one or more new tests, which describe the modified requirements either with a modified or different process model or with a stimulus from measurements. All previously defined tests ensure the controller's basic behavior, leading to higher quality for the complete system. In addition, we believe we can extend our approach to different types of real-time systems and evaluate how to use TDD for their development     

Test-Driven GUI Development with TestNG and Abbot

Testing GUIs can make the entire system safer and more robust. Any GUI, even one providing only the simplest capabilities, likely encloses some level of complexity. The more user-friendly a GUI is the more complexity it might be hiding from the user. Any complexity in software must be tested because code without tests is a potential source of bugs. A well-tested application has a greater chance of success. Several recommendations and practices can simplify test-driven GUI development for Java Swing applications. TestNG-Abbot, a developer-friendly library, provides a simple API that facilitates the application of TDD to Java GUIs     

Speed Up the Conception of Logical Systems with Test-Driven Development

In this paper, I stress the utility of employing test-driven development (TDD) for conceiving logical systems. TDD, originally invented in the context of Extreme Programming, is a methodology widely used by software engineers to conceive and develop programs. Its main principle is to design the tests of the expected properties of the system before the development phase. I argue that this methodology is especially convenient in conceiving applied logics. Indeed, this technique is efficient with most decidable logics having a software implementation. Having a clear list of the desired inferences right from the beginning makes it possible to refine the properties of the system step by step until its completion. I distinguish and detail seven advantages of the usage of TDD for the conception of a logical theory. Most importantly, this methodology increases the predictability of the inferential power of the theory. A second important benefit is that the time required for the conception of the logic goes down dramatically. This methodology will change both ideas and practices. Logic is no longer considered to be a formal science, but rather to be an empirical one. Research in the field is geared toward specific and concrete goals. Programs are considered tools used to verify the conformity of formal theories. To sum up, I defend the view that, in some situations, this way of designing a formal system brings significant benefits, and that the construction of new logics can be conducted similarly to the development of open source software.     

基于测试驱动开发的C语言教学研究

本文结合C语言课程的教学实践,提出了将测试驱动开发引入C语言教学的方法,并通过实例说明该方法能给学生提供一种全新的思维模式,帮助学生解决实际问题,提高程序编写的质量。该研究成果取得了良好的教学效果,受到学生的普遍欢迎。     

A successful application of a Test-Driven Development strategy in the industrial environment

Unit Test-Driven Development (UTDD) and Acceptance Test-Driven Development (ATDD) are software development techniques to incrementally develop software where the test cases, unit or acceptance tests respectively, are specified before the functional code. There are little empirical evidences supporting or refuting the utility of these techniques in an industrial context. Just a few case studies can be found in literature within the industrial environment and they show conflicting results (positive, negative and neutral). In this report, we present a successful application of UTDD in combination with ATDD in a commercial project. By successful we mean that the project goals are reached without an extra economic cost. All the UTDD and ATDD implementations are based on the same basic concepts, but they may differ in specific adaptations to each project or team. In the implementation presented here, the business requirements are specified by means of executable acceptance tests, which then are the input of a development process where the functional code is written in response to specific unit tests. Our goal is to share our successful experience in a specific project from an empirical point of view. We highlight the advantages and disadvantages of adopting UTDD and ATDD and identify some conditions that facilitate success. The main conclusions we draw from this project are that ATDD contributes to clearly capture and validate the business requirements, but it requires an extensive cooperation from the customer; and that UTDD has not a significant impact neither on productivity nor on software quality. These results cannot be generalized, but they point out that under some circumstances a test-driven development strategy can be a possible option to take into account by software professionals.     

Managing Large Subcontracted Projects

Monitoring any development project is a difficult task. The challenge is greater when the development project is subcontracted to an external group; the project is even more difficult when it is large. A methodology is necessary to monitor and thus establish control over the project.     

煤化工大项目DCS架构

介绍陕化煤化工有限公司化工项目的工艺流程,以及DCS控制系统的主要架构.     

Managing Software Development in Microprocessor Projects

Careful management of firmware development effort and selection of appropriate design tools can improve programmer productivity.