Earthquake Upgrade

[kraftp]

Add unit tests to the Earthquake Tracker app to demonstrate how to unit-test a DBOS app.

[chuck-dbos]

This is a good start.

The one question I have is about 'conftest.py'... it looks like something that is complex enough that it could be subject to changing best practices over time, if not outright having issues. Is there a place where we can keep the "best one", so people adding testing to existing projects can grab it?

Documentation of the process for that (packages to install, template code and where to get it) is destined for a home in our docs at some point?

[chuck-dbos]

This is a good start.

The one question I have is about 'conftest.py'... it looks like something that is complex enough that it could be subject to changing best practices over time, if not outright having issues. Is there a place where we can keep the "best one", so people adding testing to existing projects can grab it?

Documentation of the process for that (packages to install, template code and where to get it) is destined for a home in our docs at some point?

[kraftp]

This is a good start.

The one question I have is about 'conftest.py'... it looks like something that is complex enough that it could be subject to changing best practices over time, if not outright having issues. Is there a place where we can keep the "best one", so people adding testing to existing projects can grab it?

Documentation of the process for that (packages to install, template code and where to get it) is destined for a home in our docs at some point?

I'm going to write a docs page for testing today. The conftest.py is complicated because I wanted to see if you could run Alembic migrations entirely programmatically to reset your database between tests. Turns out you can, but it's not pretty. Unfortunately that has nothing to do with DBOS--it's all on Alembic--so not sure how much we can improve this.

[chuck-dbos]

I'm going to write a docs page for testing today. The conftest.py is complicated because I wanted to see if you could run Alembic migrations entirely programmatically to reset your database between tests. Turns out you can, but it's not pretty. Unfortunately that has nothing to do with DBOS--it's all on Alembic--so not sure how much we can improve this.

It's not strictly about improving it. It's about leaving ourselves room to improve it and having it be simple for people to get the latest version.

[kraftp]

I'm going to write a docs page for testing today. The conftest.py is complicated because I wanted to see if you could run Alembic migrations entirely programmatically to reset your database between tests. Turns out you can, but it's not pretty. Unfortunately that has nothing to do with DBOS--it's all on Alembic--so not sure how much we can improve this.

It's not strictly about improving it. It's about leaving ourselves room to improve it and having it be simple for people to get the latest version.

Got it! The obvious place to write down best practices like this is in the docs. I'll do that later today. Where else could we put it?

[qianl15]

Looks good as a first step. We still have room to improve the DB connection setup, but maybe in a separate PR