How do you test your product before launch?

I recently came across what the majority calls "vibe coding" and I am addicted. As I am a marketing guy, I couldn't resist in creating not one, not two, but 8 apps, which are basically systems to solve my own problems and frustrations.

However, I couldn't help but notice that all these tools are far from perfect. Lovable, Replit (which I use extensively now) say they did something, but in reality, they made only the surface.

Now, you will be quick to say that I didn't give them the correct prompt or instructions so there you have it - incomplete.

You may be right, as I am still learning.

But, I remembered the good old days I was working at a toy company and I was their "Marketing Manager" (essentially their everything guy). One of my responsibilities was to test the toys we produce.

What I remember was endless testing of electronics, voices, and flows, for a physical product that once was confirmed and entered production, there was no turning back. One mistake or oversight, and the product was totally ruined.

So creating my apps now reminds me exactly those days. I spend more time testing flows than actually creating the whole thing. And it takes time.

My process is this:

• When I was testing toys back in my 30's I used to draw the entire process on paper. Now, seems this also works for digital products, and thank God we also have ChatGTP. I work with it to create a basci structure which I then print out with tick boxes. Maybe this counterintuitive for most, but I am not used in checklists on a screen - I want to also note changes.

• I break the whole project in components, like "user authentication", "billing", "visual canvas" and once a crticila piece needs to be connected with another, I am testing this flow. Once another one does, then I retest the same flow and then the new. For exampl, lets say that I simulate a user visits the website and then decides to take a free trial. Does the clicking of the button takes him to the billing? When this does, does it redirect to the user registration? Then does it send an email and so forth. This maybe very common to you, but for a non coder it is rocket science, still

• Finally I do something many find it crazy - my old bosses used to, but they understood it. I actuall ytook this advice from John Carlton, a famous copywriter. Once I finish testing - or if testing goes wrong - I sleep on it for 2-7 days. I do something else, like building another app, or working with my clients or my staff. Lately I find extreme joy in gardening :-) Then I come back and the flow works like a charm - which means two things I was either tired and made mistakes, or the universe was against me:-(
  

What is your process? How do test your products? I would love to exchange some thoughts and possibly refine my approach.