nostr:nprofile1qqs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qgswaehxw309ahx7um5wghxcctwvsq3qamnwvaz7tmwdaehgu3wwa5kuegty9tns this is your area of expertise right?
I've never done this. Does this look like a good structure? Any comments?
https://github.com/0ceanSlim/grain/blob/main/tests%2Freadme.md
I'm using a local relay, as well, and just changed the app, so that I can use it with an "only local" setting, to test it in production through a browser bot (Playwright).
Make sure you have a deep-to-thin setup (the further you get from the code unit -> integration -> feature/e2e/smoke, the flimsier the test should be, so that you don't get steamrolled maintaining high-level test suites.
Are you running a linter or similar static test before starting the dynamic ones? They actually catch the most bugs and then you break out, earlier.
Make sure that you have steps and break out on every failed step and have a success message at the end.
If you use any AI when coding, make sure to start with a smoketest on the unit test level, that just quickly checks to make sure all core components are where you left them.
Saves a lot of headache.
