Show HN: Monito, a browser extension for software testers

by bjarocki • 5 years ago

62 29 5 years ago

atonse• 5 years ago

This looks awesome. Is the underlying recorded data available in an easy to parse format like JSON?

Would be quite powerful to do 90% of the work of transforming that recording to a puppeteer script to add to one’s test suite.

Speaking of which, what is the state of the art right now for browser automation scripts?

bjarocki12• 5 years ago

Thank you! And yes, it's all JSON. It's not super easy to read when you get all the data this way, though. I'm planning to add a web-based log reader to parse the logs and display them in the same way it's done in the extension.

Also, generating Cypress/Puppeteer/Playwright tests is on my to-do list. It should be fairly easy because all the data, including selectors, is already there. I wrote more about my plans here: https://jarocki.me/blog/monito

Regarding state of the art for browser automation scripts, I think the most popular tools are Cypress and Puppeteer. I'd like to get some feedback from QA folks, though.

Xen0byte• 5 years ago

Hi, just to chip in because I read your request for feedback and also because I'm interested in seeing what Monito can do. I’ve been heading QA depts at large tech companies for a while now, and part of my job is to be up to speed with the latest tools and trends, and to write automation tools for various tech stack layers. To answer your question, my preferred front-end tool at the moment is Playwright (via C# binding). Playwright is the new kid on the block, but it has great potential; I’ve migrated all of our Selenium tests to it and I couldn’t be happier.

topazas• 5 years ago

Any open source alternatives?

brysonreece2• 5 years ago

Yeah, I would be interested in this as well. I'm not really up for paying $39 for a half finished landing page of info built using reworded Tailwind UI components.

bjarocki12• 5 years ago

I agree. The landing page isn't the nicest one. I'm not a designer, though, and I'd rather spend that time improving the product. Is there anything you'd like to see in the extension that'd convince you to pay for it? Happy to improve!

nxpnsv3• 5 years ago

I’m also not sure exactly what’s being sold, but I don’t get why tailwind is a problem?

makarov• 5 years ago

Looks similar to https://birdeatsbug.com

cyberge99• 5 years ago

Is Firefox on the roadmap?

Would the Brave add-on work in Firefox?

bjarocki12• 5 years ago

Now I know people are interested in this so I'll be looking into adding more browsers support. I _think_ Firefox is doable. Safari most probably not (nobody cares probably, but still).

l-albertovich• 5 years ago

Disregard the style complaints, they make no sense. The tool seems super cool and I'd definitely give it a try if there was at least some sort of usage demo as it's not something that would let me do things I can't do already but something that would make it much more comfortable and to evaluate that I need to at least take a look at it.

bjarocki12• 5 years ago

Thank you! Regarding usage demo, do you mean something like video explaining what this tool can do and how is it better than existing solutions?

jacekm2• 5 years ago

May I suggest adding Jira integration?

bjarocki12• 5 years ago

It'd require storing user login data. For now, I'm not planning this, but we'll see what the future brings.

dabinat• 5 years ago

This seems to be aimed at developers / testers but it might be useful for end-users too.

If a customer reports a problem we can’t reproduce, it would be handy to just direct them to a plugin they can download to generate a report.

But the up-front pricing model doesn’t work for that kind of scenario because customers wouldn’t pay for it. It would be better to have the customer download it for free and enter a one-time code that allows them to use it under my subscription.

bjarocki12• 5 years ago

That's interesting. I'll add that to my to-do and think about possible solutions. Thank you!

mdaniel• 5 years ago

FWIW, that scenario is closer to the problem Sentry is trying to solve, and their feedback capture mechanism allows the end user to contribute anything relevant, or even just rant!, which can be helpful beyond just the raw data of an error capture

I do recognize that this tool seems like it's oriented toward logic bugs whereas Sentry really shines in the unforseen outcomes case, but I'd bet a well placed "send feedback" link could still capture the browser details and breadcrumbs without requiring a formal error per se

nxpnsv3• 5 years ago

Can i see a report somewhere?

bjarocki12• 5 years ago

Sure, https://www.dropbox.com/s/zffejt4u2l5d3x1/logs-1620070042074...

When you are extracting logs, it creates a single archive with all the items you selected. Usually, it'll be: 1. Combined logs - everything in a single file 2. Network logs 3. Console logs 4. User interactions 5. Navigation events

One user already suggested it'd be nice to include generated HTML with more human-readable logs. I thought about having a web-based log reader, but this seems to be an even better idea.

nxpnsv3• 5 years ago

Thanks, this is interesting. Yes, a pretty report would def help getting more users.

suifbwish• 5 years ago

As a developer, why would I want to use a special browser than isn’t mainstream for anything. It’s just going to need retesting in the mainstream ones and I’m not sure what this offers that grease monkey and vanilla developer tools doesn’t.

Show HN: Monito, a browser extension for software testers

Related Stories