I agree with Claude & Gemini, but I was leaning toward GPT's solution originally. I find it weird discussing coding tradeoffs and best practices with these LLMs, because I find it hard to trust them.

I feel this is an apt metaphor on why it’s important to engage and change these people’s minds rather than stop doing what you know is right. Because we don’t want them to shut you down and take power. I’m very aware, easier said than done.

And the marketing and theme of the site is 1980's synthwave meets dracula. Boom! Marketing writes itself. *drop mic*

I think the only draw back is that other tests cannot rely on this data being in the DB, since tests can run in parallel.

But proper test isolation would dictate that each test case should have it's own isolated test data anyway. So other tests shouldn't rely on data from other tests anyway.

My line of thinking of doing this before the test is to make sure the data is not already added.

We can get a dump of the DB to debug if something happens after the test runs.

We also don't rely on a cleanup hook incase the test runner crashes.

There are 2 ways to handle saving the steps.

the back end - allowing the person to pick up on any device where they left off

the client - which doesn't require any networking calls

For testing, both would require setting up data to be on the step you want to test. I'm leaning towards client.

Just another random Japanese pastry shop near there is Patisserie Fouet which is located on 9th and 52nd. So amazing. They also share the location with Raku, which is an amazing Udon restaurant. There are only a few things I miss about NYC, and the amazing Japanese food is one of them.