Relicx

Relicx

Test fast with Generative AI

5.0
6 reviews

262 followers

Introducing Relicx, your Generative AI-powered assistant to ship quality software fast. Create tests in minutes with our no-code interface, powered by cutting-edge AI. Write self-healing intent-driven tests using the natural language. Go beyond functionality—our AI autonomously identifies visual issues across your application for complete coverage. Align your tests with real-world scenarios through user session capture, ensuring the highest quality customer experience.
Relicx gallery image
Relicx gallery image
Relicx gallery image
Relicx gallery image
Relicx gallery image
Free Options
Launch Team
Vy - Cross platform AI agent
Vy - Cross platform AI agent
AI agent that uses your computer, cross platform, no APIs
Promoted

What do you think? …

Sushil Kumar
Hi 👋 Sushil here, CEO of Relicx. Today we are officially coming out of stealth and are excited to be launching here on Product Hunt! 🎉 Have you ever wondered why your customers always discover bugs and not your tests? Are you frustrated about spending countless hours firefighting production issues? If so, Relicx is the answer! Relicx enables you to: ✅ Debug front-end customer problems in minutes with session replay, dev console, and stack traces. ✅ Auto-generate end-to-end tests based on real user sessions. ✅ Ship your next release faster by measuring release readiness with a CX risk score. Interested in learning more? Sign up to try Relicx for free. We’re also giving away t-shirts and 30% off a first-year subscription to all Product Hunters this month. https://app.relicx.ai/signup#pro... Please let us know if you have any questions or feedback - we’d love to help you in your next release!
Debaditya Chatterjee
Happy and proud to be part of this amazing team !!
Gurashish Brar
RelicX is easy to deploy, has negligible overhead, can automatically create a suite of tests that captures real user engagements that will catch the bugs that matter.
Dustin Kane
FranckUxJapan
@sxkumar How long does the trial period last? How much will it cost once the trial period is over?
Sushil Kumar
Hi @franckinjapan - 30 days full feature trial and then a free forever tier limited to 1000 sessions/month.
Arnab Chakrabarty
Great explainer video! The platform sounds intriguing. I am curious though. Will the auto-generated tests work even if the app design or UI workflows change?
Rahul Lingala
@arnab_chakrabarty Amazing question. You can still execute the tests. Our product is smart enough to interpret that if a button moves from one position to another position, then it has to click the button in the new position. However, iff the whole design of the page has changed, we have the edit test feature and you can edit that particular step with just a few clicks.
Rahul Lingala
@arnab_chakrabarty While editing the test, you will be shown the video replay of the test executed in the new page and you will have the ability to pick the edited page from there. Having described this feature, would like to re-iterate that our product is "smart" enough to figure out lots of such changes by itself. You will need to use this editing feature only if there is a major change in the UI design.
Debaditya Chatterjee
@arnab_chakrabarty Thanks. Thats a great question !! Please give Relicx a try to find out that we have built Relicx with the assumption that pages change and our tests have the smarts to auto adopt to these change with no or minimal edits.
Gurashish Brar
@arnab_chakrabarty We have developed technology specifically to address this challenge of continuously changing applications and constant need to fix existing tests to match the new behaviors. If your users can navigate the new changes in your application without having to relearn how to use the product, then our tests will also adapt accordingly without requiring constant supervision. For the rare cases, the product experience seamlessly guides the developer to edit and correct the test on the spot with minimal effort.
Dustin Kane
@arnab_chakrabarty this is really where the magic happens. Relicx has this thing called "smart selectors" that use a variety of heuristics to turn DOM elements into "objects", then identifies them again by computing a "similarity score". So if you move a button to the other side of the page, or wrap it in a new div, it will still understand that it's the same "thing". This is basically the worst thing about an alternative like selenium testing because if the xpath of anything slightly changes then the test just fails.
Rohan Bavishi
This is super awesome stuff! I was particularly intrigued by the automatic generation of tests. What happens if the website design changes? Say the "Submit" button was renamed to "Next", is Relicx able to adapt/generalize the tests?
Rahul Lingala
@rohan_bavishi1 Amazing question. Our product is smart to interpret such changes and click on the "Next" button. We have extensively tested this. Feel free to give it a shot and you will be amazed :)
Debaditya Chatterjee
@rohan_bavishi1 This is a very good question. Relicx has the built-in smarts to auto-adopt to these small changes. Often UI elements move around on the page or can be renamed as you mention here but that doesn't mean you have to change your tests in Relicx.
Jack Lin
@rohan_bavishi1 Go bears! And, to answer your question, Relicx is able to adapt to website changes by analyzing elements on the page and their relationship to each other. If the changes update your webpage significantly, we also provide an easy way to manually reassign object references, so that the Next button is treated as the Submit button.
Dustin Kane
@rohan_bavishi1 this is where the fun happens! It uses a variety of heuristics like content, size, relative DOM position, even Cartesian position and euclidian distance from other elements to classify and match "objects"
Arijit Banerjee
@rohan_bavishi1 Great question. At RelicX we have taken this open research problem, gotten up to speed with all the literature on it, and solved it at an extremely compressed timescale. - We find the best page element match (this was hard) - We figure out if it was a high confidence match or if the test should stop (this is even harder, none of the existing literature address this problem) - We are able to intelligently solve the persistence problem and link objects so that parameters you defined in v1 of your webapp are not lost in the v2 of your app (pretty sure we're one of the few people in the world thinking about this)
Megalon
Very interesting. Looks like I need to instrument my app. Is there any overhead ? I will give it a try,
Sushil Kumar
@megalon Yes, a simple Javascript browser tag. https://docs.relicx.ai/instrumen...
Megalon
@sureyeaah Great !! Any framework restrictions or performance overhead ?
Sushil Kumar
@sureyeaah @megalon No framework restriction and negligible performance impact as our SDK is very lightweight and is loaded async
Megalon
@sureyeaah @sxkumar sounds good !!
Gurashish Brar
@megalon The performance and resource usage of our SDK is negligible and you will not be able to notice the difference in user experience with and without. This is also not by accident, but through focussed engineering effort to design our SDK with goal of close to zero impact.
Fazle Rahman Ejazi
Which factors does the product takes into account while calculating the CX risk score?
Sushil Kumar
@fazlerahmanejazi The release risk score is based on the number of users sessions likely to be impacted by the broken flows. More details here https://docs.relicx.ai/release-r...
Arijit Banerjee
@fazlerahmanejazi As @sxkumar said the release risk score on our dashboard is based on the percentage of broken flows / impacted user sessions. The interesting point to note here is that with traditional testing tools one has no visibility into actual coverage. With RelicX we measure how close the test suite is to actual sessions in prod and this is built into the risk score, which can shed light on coverage gaps
Isha Chaube
As someone who has worked in the field of testing, I can totally see the NEED of such platforms. Congratulations to the team for creating something incredibly relevant and useful.
Sushil Kumar
@isha_chaube Thank you.
itrytoohard
@isha_chaube Thanks. I've heard in lengths from you the pain of manual QA.. Happy to walk you through the product
Isha Chaube
@prateekk77 True. I have seen firms/clients spend some serious money on testing. Platforms like these would not only help companies save on a lot of resources (monetory and manpower) but also help them redirect these resources to better places. I remember talking to you about the product and how it's such a simple solution to a complex probelm. Great job! Super proud!
Gurashish Brar
@isha_chaube Thank you
Debaditya Chatterjee
@isha_chaube Thanks!!
Sophia Randhawa
Also, how is this product different from something like FullStory?
Debaditya Chatterjee
@sophia_randhawa Thats another good question. Although there are some commonalities in how we capture user sessions but Relicx caters to a very different problem space and a target user (the developer). Relicx will reduce time to detect issues, improve the quality of your releases, and accelerate release velocity.
Sushil Kumar
Hi @sophia_randhawa, while we do have the session replay as one of the features like Full Story, our solution goes beyond just replaying user sessions. We analyze those sessions to extract user flows and auto-generate tests to validate those flows in your CI/CD pipeline. As a result, your developers can ship new features faster and spend less time firefighting post-release fires.
Jack Lin
@sophia_randhawa Relicx and FullStory share similar roots, but Relicx is beyond a simple product that records user interactions. Relicx integrates customer interactions with devOps pipelines and generates tests from these interactions. We place great emphasis on site reliability and testing to make sure that products are shipped without breaking existing features.
Dustin Kane
@sophia_randhawa smart question. Relicx is taking it a step further by turning the sessions into tests. It's analyzing usage, but then turning those sessions into tests that it can run against your staging environment. That way, you know before your release if something a user used to be able to do still works. It's creating the tests, running them, reporting on that, integrating with CI/CD, etc.
123
•••
Next
Last