Best of luck!
Gabriel and the team are really awesome and this product is a genius idea - I'll definitely be using it at my company as it could save us a ton of work in setting up our testing pipelines.
- Alejandro :)
Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
21–30 of 42 posts
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#22Congrats on the launch! Really exciting to see this coming together :)
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#23When talking about "capturing network traffick", does that include SSE and WebSockets? If used for regression testing, how do you go about updating existing recordings?
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#24Congrats on the launch and good luck!
Reading through thus just reminded me of Datadog browser tests. It's not exactly the same, but it might be interesting to check them out.
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#25When talking about "capturing network traffick", does that include SSE and WebSockets? If used for regression testing, how do you go about updating existing recordings?
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.
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#26What 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 diff…
> 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.
That's neat.
We've only just started using Playwright, but we're surprised at how easy it is to get going; but we're also all developers. We primarily use it to test large feature flows that are hard to mock in unit tests. For example, one test logs you in, uploads a file, waits for the result, clicks on the download button and makes sure the downloaded file is what we expected. We mainly want to ensure that we don't accidentally delete or hide the login widget or the download button while working on something tangentially related.
In the example outlined above, we don't mind spinning up the backend locally, as this allows the test also to make sure the response is correct.
However, I see how being able to only test front-end code quickly and easily without the need for a backend can be helpful in many applications. Congrats on the launch, and good luck!
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#27Could you explain to me the benefit this tool offers over something like Playwright + docker-compose (which I think also does stuff like this)?
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#28Could you explain to me the benefit this tool offers over something like Playwright + docker-compose (which I think also does stuff like this)?
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.
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#29Good 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…
> most companies currently have no e2e tests I would be curious what percentage of corporate repos have any tests.
Around 15% had automated tests that run on deployments with coverage of the app. Out of those 95% were Selenium and the most of the rest tools that wrap it. Tools like Playwright or Cypress while interesting are a very small percentage of automation currently. To be fair Playwright is pretty new.
Re: Launch HN: Meticulous (YC S21) – Catch JavaScript errors before they hit prod
#30Would like to know how it differs or compares with Cypress. Is it the mocking of the network calls that makes it different?