3 ms·

We're a no-code platform for testing, if that counts. :) Should work pretty well for testing applications built with no-code tools since the same person who bui

We're a no-code platform for testing, if that counts. :) Should work pretty well for testing applications built with no-code tools since the same person who builds the app can also write tests for it. Would love to get your feedback if you do try us: https://reflect.run/ https://reflect.run/

rectang 5y ago
I just watched your 6-minute intro video and I love it. It's not what I asked for (it won't help me write tests for the Keap campaign builder, oy), but it fills a different, sorely felt need: showing non-technical people how automated tests are constructed. I can point to this video to say, "this is what I'm doing when I'm writing tests", and I think at least some of them will understand the value proposition. The more savvy ones might buy into your platform or even try constructing tests themselves. Bravo!
- tmcneal 5y ago
  Wow, thank you!
Aeolun 5y ago
15 hours per month for $300? I run a combined 120h/day on AWS for less. Maybe it makes sense for some, and if people pay you for it then that’s great, but to me I cannot see the economics of that ever working out.
- tmcneal 5y ago
  That's fair - if you compare us to raw compute we are going to be well over an order of magnitude more expensive, even with the volume discounts we offer at our "contact us for pricing" tier. Usually when folks are considering us, they're comparing us to the other alternatives which generally are either (1) have folks on staff do each regression test pass manually, (2) hire additional devs/automation engineers to build a code-based automation suite, or (3) have existing developers spend part of their time building and maintaining a code-based automation suite. When you look at the cost of those alternatives we tend to be pretty competitive. Where we're not a good fit pricing-wise is when someone wants to run very simple tests at a high volume, like running synthetic testing / monitoring scenarios in production, or for load testing.
  - Aeolun 5y ago
    Yeah, fair enough. If it wasn’t me maintaining our pipeline I can see how the value proposition quickly increases. I guess there is a happy point in between too small and too large where you have a bunch of QA, but no dedicated people to keep your pipeline up (and if things like Cypress didn’t exist, it’d be more or less impossible).

rectang 5y ago

I just watched your 6-minute intro video and I love it. It's not what I asked for (it won't help me write tests for the Keap campaign builder, oy), but it fills a different, sorely felt need: showing non-technical people how automated tests are constructed. I can point to this video to say, "this is what I'm doing when I'm writing tests", and I think at least some of them will understand the value proposition. The more savvy ones might buy into your platform or even try constructing tests themselves. Bravo!

tmcneal 5y ago
Wow, thank you!

Aeolun 5y ago

15 hours per month for $300? I run a combined 120h/day on AWS for less. Maybe it makes sense for some, and if people pay you for it then that’s great, but to me I cannot see the economics of that ever working out.

tmcneal 5y ago
That's fair - if you compare us to raw compute we are going to be well over an order of magnitude more expensive, even with the volume discounts we offer at our "contact us for pricing" tier. Usually when folks are considering us, they're comparing us to the other alternatives which generally are either (1) have folks on staff do each regression test pass manually, (2) hire additional devs/automation engineers to build a code-based automation suite, or (3) have existing developers spend part of their time building and maintaining a code-based automation suite. When you look at the cost of those alternatives we tend to be pretty competitive. Where we're not a good fit pricing-wise is when someone wants to run very simple tests at a high volume, like running synthetic testing / monitoring scenarios in production, or for load testing.
- Aeolun 5y ago
  Yeah, fair enough. If it wasn’t me maintaining our pipeline I can see how the value proposition quickly increases. I guess there is a happy point in between too small and too large where you have a bunch of QA, but no dedicated people to keep your pipeline up (and if things like Cypress didn’t exist, it’d be more or less impossible).