<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sqlite on qone.io</title><link>http://qone.io/tags/sqlite/</link><description>Recent content in Sqlite on qone.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Jun 2015 00:00:00 +0000</lastBuildDate><atom:link href="http://qone.io/tags/sqlite/index.xml" rel="self" type="application/rss+xml"/><item><title>sqlite3 in memory db for testing db functions in python</title><link>http://qone.io/posts/python-sqlite-testing-clean-state/</link><pubDate>Sat, 06 Jun 2015 00:00:00 +0000</pubDate><guid>http://qone.io/posts/python-sqlite-testing-clean-state/</guid><description>&lt;p&gt;designing a app to be as testable as posible. When writing a application that you like to, write unit tests the best options it to always on everything written for a application to not be dependent on that the application is running. Since if we can import a function and muck or just test the isolated function. One example on this is a database function, and a database. In this example i will use sqlite3 as a example. sqlite have a option to start the db in memory. This is something is very useful since you like to have a clean state of the database for every test.&lt;/p&gt;</description></item></channel></rss>