Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 42 posts

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#11

Post by kall »

Gabriel_h wrote: post #4
kall wrote: post #3

Looks like an impressive tool that makes a previously hard but useful process an order of magnitude more approachable. With waldo.io and Checkly It joins the list of QA force multipliers that would make my life, as the sole developer in a bootstrapped startup trying to punch above it's weight, much easier. First, they give me a taste with a free plan, then hit me with production pricing we still can't justify. If I h…

Thanks so much for this feedback here. You have exactly the right idea for the use case, and so we might need to scale up our replay thresholds here.

For pricing that is both "small fish" friendly and not too cheap, I like what Vercel is doing, where the smallest paid plan is basically a discount package on the pay-as-you-go pricing beyond that, especially if you use just one seat.

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#12

Post by Gabriel_h »

inglor wrote: post #9

Good luck! We tried and failed to create a “bug capture” offering in Testim.io - what helped us work with comapnies like Microsoft/Salesforce and eventually make an exit and sell to a much larger player (Tricentis) is focusing on rock-solid AI improving tests. The founder still believes the capture idea (qa capture bugs for devs) has a lot of merit but I think there are fundamental issues with anything that doesn’t r…

We are taking every scrap of luck we can get our hands on - thank you!

> Testim/QA Capture

Self-improving tests is a really interesting area. Timing is definitely an intricate issue. You probably have to layer on top of each other a bunch of different and novel techniques to get something with good signal-to-noise. We're still working on developing those out :)

Oooh, thank you for the rec. I'll make sure to ping Oren after the launch. The space is enormous and my understanding is that the rate of growth for testing tooling will exceed the rate of growth for software, which leaves QA and testing companies in a good position.

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#13

Post by Gabriel_h »

kall wrote: post #11
Gabriel_h wrote: post #4

Earlier quoted context omitted.

Thanks so much for this feedback here. You have exactly the right idea for the use case, and so we might need to scale up our replay thresholds here.

For pricing that is both "small fish" friendly and not too cheap, I like what Vercel is doing, where the smallest paid plan is basically a discount package on the pay-as-you-go pricing beyond that, especially if you use just one seat.

That's really interesting. I'll take a deeper look at their pricing - thank you!

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#15

Post by Gabriel_h »

BasilPH wrote: post #14

What do you think the pros and cons are compared to playwright.dev? The top-level features of recording, replaying, and diff-ing seem very close in my understanding.

One key difference is that with playwright you have to replay against some environment.

Meticulous captures network traffic at record-time and stubs in responses at replay-time, which removes the need for a backend environment to replay against. We also apply a little fuzziness in our replay, like how we pick and choose selectors (e.g. imagine css selectors with hashes in them, the 'same selector' will look very different between two builds).

We have a long way to go in making this robust though.

Is there anything you wish was easier when writing tests with Playwright?

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#16

Post by gary_chambers »

Congrats on the launch!

I've been looking forward to this launch for a while; I've spent a lot of time experimenting with session recording and how it can work for regression testing, reproducing bugs, measuring performance, sharing feedback during development - there is so much potential here.

> We're actively discussing open sourcing the record+replay code.

I think open source is a good call - supporting an option to self-host would make a lot of sense, since session recording will inevitably slurp up PII or sensitive data which could put off some users.

Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod

#17

Post by gary_chambers »

Gabriel_h wrote: post #5
tough wrote: post #2

Heh, I've been waiting for this Show/HN/Launch, as I applied to the company a few months back via workatastartup, and it seemed to me like this would be an awesome product. Looks very promising, wish the team the best! Catch those errors before hitting prod, sounds like the dream PS: As on open sourcing the record+replay code, I'm sure that'd be awesome, I only have this on my radar https://github.com/openreplay/open…

Thank you for the wishes here! That is very kind of you. > Open sourcing Openreplay is awesome, but we ended up building heavily on top of rrweb ( https://github.com/rrweb-io/rrweb ). Did you know they have their own documentary on the project? I only noticed that today.

Both rrweb and OpenReplay are very solid projects. I've spent the last year or so building a session recording tool, and I've scrutinised their code quite heavily. Conceptually, session recording is quite simple, but there are so many edge cases, security models (CSP, feature policies) and performances issues to overcome.

Performance is probably the area I've spent the most time thinking about: if you want to measure performance regressions in a page, instrumenting it with a session recorder is definitely a way to skew the results (for example, checking scroll position of elements during snapshotting will trigger a reflow).

Post reply on HN