Orchestrating tests on client side

Once you have made your application as client side as possible using the philosophy outlined in my previous articles

You’ll have way better time testing your application to see if it actually works

First of all make a detailed map of your applications file you wanna test

List down all the user flows and interactions possible in that setting

Using that create a test file that will test out all the interactions and user flows

Whatever doesn’t match just get it fixed

And granularity is of utmost importance here

We want logs that give us step by step compute level logs

Even if something as simple as 2 x 3 is happening we want to see it as 2 + 2 = 4 , 4 + 2 = 6

We want to see each step happening

What that allows for us is to be able to catch anything that might go wrong under the hood

It might burn a lot of your tokens in analysis but hey it’s for the best