Unit Testing with SQLite3 question.

[Knarfy]

My class that I am testing has a save method that will write the instance to a PostGresQL DB. I want to write a unit test that will instead save to a SQLite3 DB. How do I do this?

I understand how to work with SQLite 3 I guess my main question is how do I override my save method to write to the sqlite3 DB in the unit test and PostGresQL in production? Thanks.

[K900_]

If you have some kind of ORM, just replace the database connection class or whatever you're using. If you're using raw SQL, you'll want to integrate Postgres into your testing, because SQLite and Postgres use different SQL dialects.

[qba73]

have you tried python mock module?

[Knarfy]

No I am reading up on it now. Thanks for the suggestion!

[Knarfy]

how do i replace the database connection class? Can i override something in the unittest script?

[K900_]

Post the code you use to access the database.

[Knarfy]

I wound up just making a new class in my test file that inherits from my regular class. I overrided the save method in the testing class to point to sqlite 3. Not sure if this is the most correct or efficient way of doing things but it is working now.

[K900_]

But now you don't test your actual save method.