Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
11–20 of 89 posts
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#12Title should say S12 instead of S21, no?
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#13Great to see this shift! I’d be curious to hear about the comparison to https://reflect.run — I can imagine that access to the tester community is a piece of that…
The workflow for creating tests in Reflect is pretty similar to Rainforest: we both expose a "cloud browser" that loads up your webapp and you interact with that to create your tests. The biggest difference workflow-wise is that Reflect records all your actions automatically, whereas with Rainforest you often need to both specify what step you're going to take, and then actually perform that action in the browser itself. Recording everything automatically is technically harder to pull off since it's forced us to ensure we accurately record every step you take, but we think it makes for a better workflow since you can create tests faster, and there's less chance of inaccuracies that cause tests to not be repeatable.
I would quibble with the statement that you need to be far more technical to use Reflect - we're a no-code product after all. :) We have plenty of folks who aren't developers using our product. But the good thing is that both products have free tiers, so users can always give us both a try for free and decide for themselves.
Edit: Also their statement about Reflect running in headless mode is incorrect. Our test grid is a cluster of VMs: we spin up a Docker container for each test run, and each Docker container is running the test steps using a normal non-headless browser.
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#14What are some of the most important lessons you learned in building out Rainforest as a self-serve freemium product after building Rainforest as a more enterprise-focused product to start?
Good question; the enterprise focused product relied on a much more hands-on onboarding, and day-to-day support - sometimes even to the level of professional services - to use the product. Moving to self-serve exposed all of the hard-edges of Rainforest, especially around on-boarding - and later around general use of it. This forced us to up-our-game product design wise significantly, which wasn't a strong focus befo…
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#15This is a brilliant idea and direction. Congrats on launching this. How do you deal with things like permissions, proprietary information, etc?
Depending on what you mean; assuming it's the security angle:
TLDR; carefully
At a high level, most of our customers are testing in QA - not production - so usually the only proprietary information (outside of credentials to access it) we'd see is something they'd be releasing shortly anyway. However, we take security seriously;
Our infrastructure and code is heavily tested + reviewed before shipping, as well as externally audited yearly. Currently we're checked yearly for HIPAA, and from this have strong internal controls / processes, documentation and guidelines around access controls, how-things-are-done, and audited. Everything is encrypted at rest and transit (db, logs, images, etc). All the testing is done through our infra, recorded (video, kvm) and logged (http, https, dns, etc). Obviously we never re-use a VM, they're destroyed post use.
From the crowd side, they test using the same machines as automation uses (i.e. all the same logging levels as above). Additionally, each individual is KYC'd and signs an NDA with us before they can work. Enterprise, or folks needing BAAs have a sub-crowd with extra levels of KYC / other requirements.
We're currently early in starting being formally SOC 2, but it's not complete. More details here - https://go.rainforestqa.com/rs/601-CFF-493/images/Rainforest...
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#16Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#17Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#18I remember working with Rainforest back in 2016 when I was at Zentail, glad to see you guys are still alive and doing well!
Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#19Re: Launch HN: Rainforest QA (YC S12) – No-Code UI Test Automation
#20Great to see this shift! I’d be curious to hear about the comparison to https://reflect.run — I can imagine that access to the tester community is a piece of that…
Hey there - I'm one of the co-founders of Reflect so just to give my perspective: The workflow for creating tests in Reflect is pretty similar to Rainforest: we both expose a "cloud browser" that loads up your webapp and you interact with that to create your tests. The biggest difference workflow-wise is that Reflect records all your actions automatically, whereas with Rainforest you often need to both specify what s…
And totally agreed, both products take a slightly different approach and have different strengths and weaknesses, try them both and see which is a better fit!