Editing SQLite (section)

==Development and distribution==
SQLite's code is hosted with [[Fossil (software)|Fossil]], a [[distributed version control system]] that uses SQLite as a local cache for its non-relational database format, and SQLite's SQL as an implementation language.<ref>{{cite web|url = https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|title = Thoughts On The Design Of The Fossil DVCS|publisher = Fossil-scm.org|date = July 12, 2017|access-date = October 14, 2022|archive-date = October 13, 2022|archive-url = https://web.archive.org/web/20221013234319/https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|url-status = live}}</ref><ref>{{cite web|url = https://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|title = Fossil: Fossil Performance|publisher = Fossil-scm.org|date = August 23, 2009|access-date = September 12, 2009|archive-date = October 9, 2009|archive-url = https://web.archive.org/web/20091009054952/http://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|url-status = live}}</ref>

SQLite is [[Public-domain software|public domain]], but not "open-contribution", with the website stating "the project does not accept patches from people who have not submitted an [[affidavit]] dedicating their contribution into the public domain."<ref>{{Cite web |title=SQLite Copyright |url=https://sqlite.org/copyright.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-03-15 |archive-url=https://web.archive.org/web/20240315172355/https://sqlite.org/copyright.html |url-status=live }}</ref> Instead of a [[code of conduct]], the founders have adopted a [[ethical code|code of ethics]] based on the [[Rule of Saint Benedict|Rule of St. Benedict]].<ref>{{Cite web |title=Code Of Ethics |url=https://sqlite.org/codeofethics.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-02-19 |archive-url=https://web.archive.org/web/20240219225117/https://sqlite.org/codeofethics.html |url-status=live }}</ref> 

A standalone [[Console application|command-line]] [[Shell (computing)|shell]] program called ''sqlite3''<ref>{{cite web|url = https://sqlite.org/cli.html|title = Command Line Shell For SQLite|publisher = Sqlite.org|access-date = October 14, 2022|archive-date = October 6, 2022|archive-url = https://web.archive.org/web/20221006104551/https://sqlite.org/cli.html|url-status = live}}</ref> is provided in SQLite's distribution. It can be used to create a database, define tables, insert and change rows, run queries and manage an SQLite database file. It also serves as an example for writing applications that use the SQLite library.

SQLite uses automated [[regression testing]] prior to each release. Over 2 million tests are run as part of a release's verification. The SQLite library has 156,000 lines of source code, while all the test suites combined add up to 92 million lines of test code. SQLite's tests simulate a number of exceptional scenarios, such as power loss and I/O errors, in addition to testing the library's functionality. Starting with the August 10, 2009 release of SQLite 3.6.17, SQLite releases have 100% branch test coverage, one of the components of [[code coverage]]. SQLite has four different [[Test harness|test harnesses]]: the original public-domain TCL tests, the proprietary C-language TH3 test suite, the SQL Logic Tests, which check SQLite against other SQL databases, and the dbsqlfuzz proprietary [[fuzzing]] engine.<ref name="tests">{{cite web |title=How SQLite Is Tested |url=https://sqlite.org/testing.html |url-status=live |archive-url=https://web.archive.org/web/20091006224147/https://sqlite.org/testing.html |archive-date=October 6, 2009 |access-date=September 12, 2009 |publisher=SQLite.org}}</ref>