Questions that are unclear or need more context!
I’ve grouped together questions I can kinda vaguely answer because I don’t have enough clarity or context on the question itself. Feel free to message me or reply to this with further details!
I’m not sure what you mean by “structure” - do you mean like file structure of your automation, or the structure of the tests/checks themselves?
That’s a LOT of endpoints for one repository! I guess with file structure, I’d set it up like the api controllers themselves (so files for each endpoint). If you have a lot of checks for each endpoint, maybe divide that up as well - smoke checks (those that don’t make any changes) and functional checks (those that make changes). Definitely have shared utility methods to do the checking for various things, and utilize parameterization where you can. It’s hard to say more specifically without details!
I think they both have their merits. I think there are some details here I’m not getting that would better inform an answer. I hate to say “it depends” but it really does! Feel free to provide more detail and I’ll try to answer better
I have no idea lol I wish I could time travel… not sure what you’re referring to here unfortunately
I’m not super clear on the question here, but if you’re just looking to make sure tables are populated and there’s no existing API endpoint, you can query the database (assuming you have access to do so)…
I’m not sure what you mean by methodology here, like functional vs non-functional? All of the above really! An API can and should be tested like any other application.
I’m not sure the question here - basic API testing would be testing each available method (GET/POST/PUT/DELETE/PATCH/etc) for a given endpoint, yes.