Live data from Hacker News

Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

news.ycombinator.com

41–50 of 89 posts

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#41
post #38

>>> slow down or pause the release process to do QA, or move faster at the expense of product quality This is a constant dilemma for Solopreneurs/very small teams. I was just thinking last week - can I find an affordable automated testing platform (need to run tests on new features that I've added to my latest project - an Electron App). Follow up question - does this work for Electron Apps? Either way, still happy t…

Yes, it works for electron apps. You'll need to host the binary somewhere, then install it. You can bundle those actions in to one test and then reuse as a building-block for your actual tests.

Got it. Thanks

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#42
post #27

What is the benefit of "no-code"? The benefit of using code is that you have to know what you are doing. Having experienced what happens when people build data driven systems out of building blocks, with out a thorough understanding of what they are doing (brittle, failing is strange ways under load, general unreliability and low quality) I am suspicious

Agree, no-code seems to optimize for a large number of people being somewhat effective, but with less control over the output (increasing fragility, rework)

Code is more upfront effort but more control and thus less fragility but more maintainable over time (if done right).

I imagine there are some/many situations where throwing many people at a problem is the “best” way and this would suit that quite well I guess.

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#44

Does this work with desktop apps ?

Yes; you can download and install anything, then test it . Ideally you setup the install process as one test, then embed in other tests for better maintainablity. For very large apps, or long to install, we can/have Pre installed things on customized VMs for enterprise folks.

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#45
post #28

Earlier quoted context omitted.

At least for testing, and traditional automation (aka code) the bar is knowing what you're doing AND knowing the product enough to be able to test it effectively. We remove the code requirement, making testing accessible to more folks - i.e. product managers and product designers who have great knowledge of the product, but don't want to or can't code. Also, this doesn't tend to exclude developers either. Currently o…

Completely agree that testing should be more accessible to product managers and designers, and love the concept. Consider the simple example of a web form with multiple `input` elements - if I use your product to click on each input and configure a QA procedure, how does the system unambiguously identify each input given that the page layout may change in the future? The current code-based testing frameworks force me…

It identifies things visually, and optionally with OCR as well. If it moves likely no issue. Changing shape or size too much, as well as not matching OCR can cause failures - as expected. If it is an expected update and the test needs updating, we smartly suggest updates to the target if we can find one. Alternatively we have a crowd-based service to help write abs maintain your tests; it’s usually used by teams needing high leverage when managing a lot of tests.

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#46
post #27

What is the benefit of "no-code"? The benefit of using code is that you have to know what you are doing. Having experienced what happens when people build data driven systems out of building blocks, with out a thorough understanding of what they are doing (brittle, failing is strange ways under load, general unreliability and low quality) I am suspicious

Agree, no-code seems to optimize for a large number of people being somewhat effective, but with less control over the output (increasing fragility, rework) Code is more upfront effort but more control and thus less fragility but more maintainable over time (if done right). I imagine there are some/many situations where throwing many people at a problem is the “best” way and this would suit that quite well I guess.

In my experience, many orgs that work with Selenium and its derivatives have described that (coded) approach as flaky / brittle (i.e., fragile).

Of course, until automation gets to be as clever of humans, any test automation approach is going to have some flavor of brittleness.

Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation

#47
Chiming in as a happy Rainforest user. This tool has been a huge benefit to our startup. It is a great way to maintain ongoing QA at a minimum cost of hours while iterating your product, and the built-in ability to get your test fixed by Rainforest for a few bucks or to have certain tests done by hand at an hourly rate is extremely useful and makes it simple to quantify the cost of outsourcing to rainforest vs doing something inhouse.

This tool makes the benefits of a well-built automated testing setup much more accessible and less costly.

We had previously been using traditional automated QA tools like selenium when someone suggested Rainforest and I am very happy we made the switch. Nothing but praise and well wishes for this team - you are en route to massive success.

Post reply on HN