Add skeleton for backend tests and tests for authentication and swagger doc

[rlivings39]

This is what I think should be the last step to finish off #2 for user authentication.

I made a few restructuring changes like moving the sqlite setup to a package so I could call it from Python.

Let me know what y'all think!

2 big questions I had

1. Does the way I'm overriding DB_FILENAME, DB_URL in conftest.py look ok? Any other suggestions?
2. @hattifnatt4r do you think we should add github actions to the repo to run the backend and frontend tests or will that be too much for the class? Adding it in is pretty easy from a technical perspective and will ensure things don't regress.

[RyanSchofield]

I left a few comments, but looks great to me as is!

[RyanSchofield]

This looks good to me, or at least I can't see any reason not to do it like this.

Just some random musing: We could have some abstraction around accessing config files. Like a class that would accept argument (or maybe check environment variable?) on init to read from either a prod config, or test config, etc. then have methods for accessing config values. Probably overkill at this point.

[rlivings39]

I'm liking this idea of wrapping things in a class/function. Will ponder that and chat w/ Maria today about how she used to use multiple files.

[hattifnatt4r]

1. Does the way I'm overriding DB_FILENAME, DB_URL in conftest.py look ok? Any other suggestions?

Looks good to me! Another way I can think of is:

• making a config_example.py file with example values
• require developers to create config_example.py locally (config.py is ignored by git, so developers can use different setups without conflicts)
• the scripts use config.py instead of config_example.py

It adds an extra step in the dev setup and server setup (we did this at my previous job), not sure if that's needed for our group.

[hattifnatt4r]

@hattifnatt4r do you think we should add github actions to the repo to run the backend and frontend tests or will that be too much for the class? Adding it in is pretty easy from a technical perspective and will ensure things don't regress.

I think that would be great - but you'll need to teach us how to maintain this setup 🙂

[rlivings39]

@hattifnatt4r added the CI definition for this server that are passing:

https://github.com/cambridge-devclass/ambient-app--react/actions/runs/18110255663/job/51534679207?pr=27

If you're cool with this change, I'd say we merge this and then can discuss if we want to rework how the config is imported.

[hattifnatt4r]

@hattifnatt4r added the CI definition for this server that are passing:

https://github.com/cambridge-devclass/ambient-app--react/actions/runs/18110255663/job/51534679207?pr=27

If you're cool with this change, I'd say we merge this and then can discuss if we want to rework how the config is imported.

Sure that should be good, thank you!

[hattifnatt4r]

Looks good to me, thank you!