QA/Staging Tips & Observability · Builder’s Console Log 🛠️

QA/Staging Tips & Observability

Hey guys -

I've seen you mention the idea of QA/Staging environments a few times. Going through this process for the first time with an app I hope to deploy to production soon.

I am curious how you structure your QA/Staging tests?

Currently I have a staging branch on Vercel, and I've used Codex High to look at all the app's features and create a matrix that specifies what to test for each feature/component of the app, how that test is to be performed (Playwright, Cursor Browser etc) and what success criteria are.

Then Composer has gone through and performed all these automated tests. Some are still manual that I need to do.

Composer's basically found a lot of bugs/errors, which it's fixing in the staging codebase.

My plan is then to do this, finish the manual tests and then deploy to production.

Is this general an acceptable way to run QA/Staging or am I missing something mega here?

6 comments

QA/Staging Tips & Observability