Re: [sqlite] Ratio of test code to database code

2010-11-12 Thread Samuel Adam
On Fri, 12 Nov 2010 13:09:07 -0500, Simon Slavin wrote: > On 12 Nov 2010, at 4:25pm, Dr. David Kirkby wrote: > >> I think in general mathematical software like Sage is very difficult to >> test. > > Yes, I read your response and agree with this. But it's worth pointing

Re: [sqlite] Ratio of test code to database code

2010-11-12 Thread Simon Slavin
On 12 Nov 2010, at 4:25pm, Dr. David Kirkby wrote: > I think in general mathematical software like Sage is very difficult to test. Yes, I read your response and agree with this. But it's worth pointing out that commercial maths applications like MatLab /do/ have testing like that. That's

Re: [sqlite] Ratio of test code to database code

2010-11-12 Thread Dr. David Kirkby
On 11/11/10 02:32 PM, Simon Slavin wrote: > > On 11 Nov 2010, at 1:41pm, Dr. David Kirkby wrote: > >> On 11/10/10 04:28 PM, Roger Binns wrote: >> >>> The SQLite developers decided their library will always be reliable and >>> greatly care about data integrity hence the amount of testing. >> >> I

Re: [sqlite] Ratio of test code to database code

2010-11-11 Thread Simon Slavin
On 11 Nov 2010, at 1:41pm, Dr. David Kirkby wrote: > On 11/10/10 04:28 PM, Roger Binns wrote: > >> The SQLite developers decided their library will always be reliable and >> greatly care about data integrity hence the amount of testing. > > I wish the Sage developers would take as much care.

Re: [sqlite] Ratio of test code to database code

2010-11-11 Thread Dr. David Kirkby
On 11/10/10 08:58 PM, Samuel Adam wrote: > On Wed, 10 Nov 2010 08:53:40 -0500, Dr. David Kirkby > wrote: > >> Someone recently said he felt that a test:code ratio of 1:1 is about >> optimal, so > > Where do people get notions like this? Cf.: I don't know. In fact, I

Re: [sqlite] Ratio of test code to database code

2010-11-11 Thread Dr. David Kirkby
On 11/10/10 04:28 PM, Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/10/2010 05:53 AM, Dr. David Kirkby wrote: >> Someone recently said he felt that a test:code ratio of 1:1 is about optimal, > > That of course is bunk. That was my feeling too. > The optimal

Re: [sqlite] Ratio of test code to database code

2010-11-10 Thread Samuel Adam
On Wed, 10 Nov 2010 08:53:40 -0500, Dr. David Kirkby wrote: > Someone recently said he felt that a test:code ratio of 1:1 is about > optimal, so Where do people get notions like this? Cf.: : Someone recently said he felt that programmer productivity is about :

Re: [sqlite] Ratio of test code to database code

2010-11-10 Thread Simon Slavin
On 10 Nov 2010, at 4:28pm, Roger Binns wrote: > However some environments can not adequately run TCL to test SQLite which is > why there is TH3 that does the tests in C. That C code is generated with > control over how it is done as for example having it all done at once may > produce something

Re: [sqlite] Ratio of test code to database code

2010-11-10 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/10/2010 05:53 AM, Dr. David Kirkby wrote: > Someone recently said he felt that a test:code ratio of 1:1 is about optimal, That of course is bunk. The optimal amount depends on what the project does, the resources available, the consequences of

[sqlite] Ratio of test code to database code

2010-11-10 Thread Dr. David Kirkby
Sorry if this is a bit off topic, but I read from http://www.sqlite.org/testing.html that your test code is 647 time bigger than the database code. I've often pointed developers of the Sage maths software to your link. I feel more attention should be paid to testing Sage, and less to adding