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 reproduce timing perfectly (some do like Firefox’s replay.
I’m not with Testim anymore but still very excited people tacking this problem and I warmly recommend pinging Oren@testim.io (the founder, an engineer, a GDE and a nice guy) for pointers - he likes giving free advice and investing in new players in the space to cultivate the ecosystem (most companies currently have no e2e tests)
We are taking every scrap of luck we can get our hands on - thank you!
> Testim/QA Capture
Self-improving tests is a really interesting area. Timing is definitely an intricate issue. You probably have to layer on top of each other a bunch of different and novel techniques to get something with good signal-to-noise. We're still working on developing those out :)
Oooh, thank you for the rec. I'll make sure to ping Oren after the launch. The space is enormous and my understanding is that the rate of growth for testing tooling will exceed the rate of growth for software, which leaves QA and testing companies in a good position.
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.
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 reproduce timing perfectly (some do like Firefox’s replay.
I’m not with Testim anymore but still very excited people tacking this problem and I warmly recommend pinging Oren@testim.io (the founder, an engineer, a GDE and a nice guy) for pointers - he likes giving free advice and investing in new players in the space to cultivate the ecosystem (most companies currently have no e2e tests)