Unit Test 筆記-introduction

1.1 Coding With Condence

Dale would write a new routine and a short test to go alongwith it.

Nothing fancy, just a simple test to see if the routine just written actually did what it was supposed to do.

It took alittle longer to think of the test, and write it, but Dale refused to move on until the new routine could prove itself

1.2 What is Unit Testing?

Unit tests are performed to prove that a piece of code does what the developer thinks it should do.

After all, if we aren't sure the code is doing what we think,then any other forms of testing may just be a waste of time.

1.3 Why Should I Bother with Unit Testing?

Unit testing will make your life easier . It will make your designs better and drastically reduce the amount of time you
spend debugging.

When basic, low-level code isn't reliable, the requisite xesdon't stay at the low level. You x the low level problem, but
that impacts code at higher levels, which then need xing,and so on. Fixes begin to ripple throughout the code, getting
larger and more complicated as they go. The house of cardsfalls down, taking the project with it

1.4 What Do I Want to Accomplish?

Many developers who claim they do testing only ever write onetest. That's the test that goes right down the middlE

Code that you can't depend on is useless. Worse, code thatyou think you can depend on (but turns out to have bugs) can
cost you a lot of time to track down and debug. There arevery few projects that can afford to waste time, so you want to
avoid that “one step forward two steps back” approach at all costs, and stick to moving forward.

It's not polite to expect others to clean up our own messes,
and in extreme cases submitting large volumes of buggy code
can become a “career limiting” move.
On the other hand, if the testers or QA group nd it very
difcult to nd fault with your code, your reputation will grow
rapidly—along with your job security!