Tweet
Did a quick check: generating the test files works pretty well!

But the beta tester’s app uses drag and drop behaviour so I need to add events for that 🤦‍♂️

#buildinpublic
POC is live and collecting data on the first beta user’s dev environment.

Once there’s enough data, I *should* be able to generate a Cypress suite for the app with minimal manual input 🤞.

#buildinpublic
Scheduled another demo with an ex colleague. Planning to go over the data collection and Cypress file generation.

Hopefully it’ll lead to a few more intros!

#buildinpublic
POC data collection working nicely. Now back to outreach.

#buildinpublic
Found a bit more time to work on the MVP but got stuck establishing the sockets connection. It works fine locally but not after deploying. 🤔

#buildinpublic
Progress so far:

- Script that records user interactions and streams them to server via sockets deployed to S3.
- Simple app to receive event data and save to DB finished but not quite deployed.

#buildinpublic
Started on the data-collection part of the MVP. It will be good to get some live data and experiment with generating the test files.

Mustn’t let this distract me from interviews though!

#buildinpublic
A founder friend of mine agreed to let me use his app as a test case. I can add the widget to his site to start collecting anonymised event data.

He’s quite interested in a user journey breakdown but not so much in getting the test files. 🤔

#buildinpublic
Still waiting on intros to more QAs from my last user interview. Forced myself to be pushy and sent a follow-up email.

#buildinpublic
Getting interviews is quite slow progress. While I’m waiting on intros I scoped out an MVP:

JS widget to collect event data and a manual email with user journey breakdown and test files.

I can manually parse the data and write the tests for now.

#buildinpublic
Trying to overcome my awkwardness and use my network to get user interviews with Test Engineers. Reached out to a few ex-colleagues on LinkedIn and asked to chat or for intros.

#buildinpublic
Had my 2nd interview with a QA. This time tried to be even more specific with questions.

Similar response to the first. But this time mentioned digging into APIs to understand how to stub responses as a pain point. Again happy to intro me to a few people.

#buildinpublic
Interviewed a QA I used to work with. Tried to stick to The Mom Test: don’t mention the product and ask for time/money/reputation.

In general, quite positive. Identifying critical business flows is a pain point. And they were happy to intro me to someone else.

#buildinpublic
Cold emailed ~15 indie founders to do some validation. Kept it simple and just said a quick hello and asked if they have automated tests. Seems quite effective way to open conversations.

Main takeaway was that tests aren’t a top priority for solo founders.

#buildinpublic