1. the logs hopefully tell you where to look
2. the logs hopefully give you enough context to construct a physical test (ie, replicate)
3. the physical test hopefully gives enough context to write an automated test
4. we write the automated test, submit to staging, do the physical test again
5. PROFIT!
In my experience logs are rarely enough for browser automation issues.
I usually end up reproducing the actual session manually because timing/state problems often don’t show up clearly in logs.
yeah those are especially nasty. the logs are cryptic and not helpful when most of the the issues will be seen visually in the browser
we don't lol, we used to do but these day everyone is doing vibe coding and nobody looking at the logs or error but i use sentry for my side project
yeah time to pipe it into claude and tell me what is wrong
Certain bugs don’t really make sense until you interact with the real system
yeah that's kinda how I feel but wanted to see other's experience
1. the logs hopefully tell you where to look 2. the logs hopefully give you enough context to construct a physical test (ie, replicate) 3. the physical test hopefully gives enough context to write an automated test 4. we write the automated test, submit to staging, do the physical test again 5. PROFIT!
PROFIT BABYYY