How to Prevent JavaScript TypeErrors
1 points • 0 comments
@Gabriel_h | Hacker News
From 1/6/2015, 2:59:23 PM till now, @Gabriel_h has achieved 85 Karma Points with the contribution count of 54.
Recent @Gabriel_h Activity
JavaScript Range Errors and how to prevent them
1 points • 0 comments
Hey HN, I'm Gabriel, founder of Meticulous (YC S21). Our mission is to make the world's code safe, performant and reliable.
We're starting with a tool to catch JavaScript regressions in web applications with zero-effort from developers.
How it works: Insert a single line of JavaScript onto your site, and we record thousands of real user sessions. We then replay these sessions on new code to automatically catch bugs before they hit production. You can watch a 60-second demo at https://www.meticulous.ai.
Catching JavaScript regressions is just the start. We are a London-based YC company. Our team previously worked at Dropbox, Opendoor and Google. We raised $4m, and are backed by some of the best founders and technical leaders in Silicon Valley, including Guillermo Rauch (founder Vercel, author next.js), Jason Warner (CTO GitHub), Scott Belsky (CPO Adobe), Calvin French-Owen (founder Segment), Jared Friedman (YC partner and former CTO of Scribd) and a bunch of other incredible folks.
You can read more at https://www.ycombinator.com/companies/meticulous/jobs/AkHpFa...
If interested please feel free to reach out to me at gabe at meticulous dot ai, with a few lines on what interests you about Meticulous and mention HN in the subject line.
It really depends on your use-case here.
If you’re able to spin up an environment via docker-compose and play against that with playwright, then I think that’s good for that use-case.
However, if you’re testing a flow that relies on some initial state, it can sometimes be tricky to seed that state or do so in a way which is representative.
It does not include SSE or WebSockets.
With regards to updating existing records, unfortunately we don't currently have good tooling & support for this, so you may need to record new sets of sessions as your application changes. I would suggest starting off with testing a few core flows.
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?
That's really interesting. I'll take a deeper look at their pricing - thank you!
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.
Ouch, that does sound like a painful cycle. It happens, and no one tests as much as they'd like to.
> Portability of the data.
I hear your concern here. The replay data and session data is also saved to disk, so you can save this somewhere. Of course that still leaves the risk of the record & replay tech. I think open sourcing this would solve the portability issue here, and it's something we're actively talking about but haven't reached a conclusion on yet. Anecdotes and examples like this though are incredibly helpful in helping us make that decision.
Thank you for the feedback!
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.
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.
Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
122 points • 40 comments
Axios vs. Fetch
1 points • 0 comments
Meticulous | #2 Founding Engineer | London | Full-time | Onsite | Visa sponsorship available | £100k - £160k+, 0.5% - 3%+ ($150k - $900k+ equity)
Hey HN, I'm Gabriel, founder of Meticulous (YC S21). Our mission is to make the world's code safe, performant and reliable.
We're starting with a tool to catch JavaScript regressions in web applications with zero-effort from developers.
How it works: Insert a single line of JavaScript onto your site, and we record thousands of real user sessions. We then replay these sessions on new code to automatically catch bugs before they hit production. You can watch a 60-second demo at https://www.meticulous.ai.
Catching JavaScript regressions is just the start. We are a London-based YC company. Our team previously worked at Dropbox, Opendoor and Google. We just raised $4m, and are backed by some of the best founders and technical leaders in Silicon Valley, including Guillermo Rauch (founder Vercel, author next.js), Jason Warner (CTO GitHub), Scott Belsky (CPO Adobe), Calvin French-Owen (founder Segment), Jared Friedman (YC partner and former CTO of Scribd) and a bunch of other incredible folks.
You can read more at https://www.ycombinator.com/companies/meticulous/jobs/AkHpFa...
If interested please feel free to reach out to me at gabe at meticulous dot ai, with a few lines on what interests you about Meticulous and mention HN in the subject line.
How to set up visual regression testing
1 points • 0 comments
How to Prevent Visual Regressions
2 points • 0 comments
Meticulous | #2 Founding Engineer | London | Full-time | Onsite | Visa sponsorship available | £100k - £150k+, 2%+
Hey HN, I'm Gabriel, founder of Meticulous (YC S21). Our mission is to make the world's code safe, performant and reliable.
We're starting with a tool to catch JavaScript regressions in web applications with zero-effort from developers.
How it works: Insert a single line of JavaScript onto your site, and we record thousands of real user sessions. We then replay these sessions on new code to automatically catch bugs before they hit production. You can watch a 60-second demo at https://www.meticulous.ai.
Catching JavaScript regressions is just the start. We are a London-based YC company. Our team previously worked at Dropbox, Opendoor and Google. We just raised $4m, and are backed by some of the best founders and technical leaders in Silicon Valley, including Guillermo Rauch (founder Vercel, author next.js), Jason Warner (CTO GitHub), Scott Belsky (CPO Adobe), Calvin French-Owen (founder Segment), Jared Friedman (YC partner and former CTO of Scribd) and a bunch of other incredible folks.
You can read more at https://www.ycombinator.com/companies/meticulous/jobs/AkHpFa...
If interested please feel free to reach me at gabe at meticulous dot ai, with a few lines on what interests you about Meticulous and mention HN in the subject line.
The Problem with JavaScript's Unshift
1 points • 0 comments
Let users write your tests for you
4 points • 0 comments
Transforming JavaScript logging from a bad habit to best practice
6 points • 0 comments
site design / logo © 2022 Box Piper