in reply to Test/ Code Ratio
I don't think the test/code ratio is a useful measurement. If there's a useful measurement of the amount of tests, it is related to the pre- and postconditions. Or, if you will, the amount of flexibility. To take it to the extreme, if something is supposed to do one thing, all you need is one test. No matter how much code you've written. If pressing a button means the lights go on, and pressing it again means the lights go out, you only need two test cases:
- Press button. Success iff lights go on.
- Press button again. Success iff lights go off.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Test/ Code Ratio
by BrowserUk (Patriarch) on Jan 28, 2005 at 16:24 UTC | |
by xdg (Monsignor) on Jan 28, 2005 at 20:37 UTC | |
by BrowserUk (Patriarch) on Jan 28, 2005 at 22:08 UTC | |
by Aristotle (Chancellor) on Jan 28, 2005 at 23:06 UTC | |
by Aristotle (Chancellor) on Jan 28, 2005 at 22:10 UTC | |
| |
by petdance (Parson) on Jan 31, 2005 at 03:13 UTC | |
by BrowserUk (Patriarch) on Jan 31, 2005 at 04:57 UTC | |
Re^2: Test/ Code Ratio
by moot (Chaplain) on Jan 28, 2005 at 20:45 UTC |
In Section
Meditations