-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|697|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
SoCoder -> Link Home -> Dev-News


 
HoboBen
Created : 21 April 2010
 

SQLite - source code to test code - ratio of 1:679



https://www.sqlite.org/testing.html?1
The reliability and robustness of SQLite is achieved in part by thorough and careful testing.

As of version 3.6.23 (all statistics in the report are against that release of SQLite), the SQLite library consists of approximately 67.2 KSLOC of C code. (KSLOC means thousands of "Source Lines Of Code" or, in other words, lines of code excluding blank lines and comments.) By comparison, the project has 679 times as much test code and test scripts - 45678.3 KSLOC.

 

Comments


Wednesday, 21 April 2010, 02:22
Jayenkai
Geeeze!!!
My code's never that bloated. I rarely comment!
Wednesday, 21 April 2010, 02:51
JL235
The more testing the better, but there comes a point when you have too many tests. I can imagine lots of their time must be put into maintaining those tests and ensuring they are up to date with any API changes.