Development log - red & black (1)

王朝other·作者佚名  2006-01-08
宽屏版  字体: |||超大  

Development log - red & black (1)

Red

Software that easy to test.

By Zhang Hui

Mr Z add some backdoor in the debug version of software. He even add a small

console for the application. It's more easy for him to do some kind of testing.

For example, if we want to test the case of what display when there are over

10000 message. No one will send 10000 message to do such test, it's so expensive

and time-consuming! What he does is add a small language parser in the application.

When inputting words can be parsed by the small language engine, it will trigle

some actions. Because it supports parameters, it's very handy for us to do various

testing. What a great idea! Supposing we add "add inbox 1000", that means to create

1000 messages and store them in inbox. It's so easy, isn't?

Yesterday, I read the chapter of "unit test" of "Dive into python". From the example,

we know that the more early we add "unit test", the more we can get from them.

By "testing first", we can avoid over-design, we can release ealier, we can code

with full confidence, we can code in a graceful way, we can refactor the code anytime,

anywhere without worry about break something else.

To write a programe is not difficult, While it's much more difficult and complicated

to finish a "software". The core idea of developing software is to ensure quality,

meet schedule, within bugdet. So the core of the core is the software quality.

An procedure or mechanism is needed to ensure quality. It's natural for me to adopt

the idea of "test driven development" or "test centered development".

The mature level of development is decided by the level of testing.

===================================

版权所有 \copyright张辉 2003

本文可原封不动的拷贝和自由地再发行,但在拷贝和再发行的拷贝中必须

原封不动地含有这段版权声明。

http://forestsong.blogone.net

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
© 2005- 王朝网络 版权所有