요즘 읽고 있는 책.
TDD는 어떠한 경우에도 유용한 개발방법론이고 따로 개발방법론이라고 부르지 않더라고 개발자의 생활이되는 날이 올것이라 믿습니다. 어떻게 숨쉬는지 가르치는 책이 없듯이 우리 아들이 컷을때는 왜 이런것이 책으로 따로 배워야하는 건지 묻게될터.
http://www.throwtheswitch.org/ ; Unity, C unit test
http://www.jamesgrenning.com/ ; author's website
----------------
Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards. Kent Beck, who is credited with having developed or 'rediscovered'[1] the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.[2]
Test-driven development is related to the test-first programming concepts of extreme programming, begun in 1999,[3] but more recently has created more general interest in its own right.[4]
Programmers also apply the concept to improving and debugging legacy code developed with older techniques.[5]
https://en.wikipedia.org/wiki/Test-driven_development
----------------
*Google book review
Another day without Test-Driven Development means more time wasted chasing bugs and watching your code deteriorate. You thought TDD was for someone else, but it's not! It's for you, the embedded C programmer. TDD helps you prevent defects and build software with a long useful life. This is the first book to teach the hows and whys of TDD for C programmers.
TDD is a modern programming practice C developers need to know. It's a different way to program---unit tests are written in a tight feedback loop with the production code, assuring your code does what you think. You get valuable feedback every few minutes. You find mistakes before they become bugs. You get early warning of design problems. You get immediate notification of side effect defects. You get to spend more time adding valuable features to your product.
James is one of the few experts in applying TDD to embedded C. With his 1.5 decades of training,coaching, and practicing TDD in C, C++, Java, and C# he will lead you from being a novice in TDD to using the techniques that few have mastered.
This book is full of code written for embedded C programmers. You don't just see the end product, you see code and tests evolve. James leads you through the thought process and decisions made each step of the way. You'll learn techniques for test-driving code right nextto the hardware, and you'll learn design principles and how to apply them to C to keep your code clean and flexible.
To run the examples in this book, you will need a C/C++ development environment on your machine, and the GNU GCC tool chain or Microsoft Visual Studio for C++ (some project conversion may be needed).
----------------
'Programming' 카테고리의 다른 글
| Visual Studio 2015 제품군 (0) | 2015.11.19 |
|---|---|
| Hard core Embedded Programming - no printf() sprintf() (0) | 2015.11.19 |
| C++ reference link (0) | 2015.10.31 |
| C언어 레퍼런스 (0) | 2015.10.25 |
| Eclipse for C/C++ (0) | 2015.10.17 |
