Iris lets you test websites and apps without writing complex code. Describe your tests in English, and Iris handles the rest. Whether you're checking if buttons work, pages load correctly, or testing overall performance, Iris makes it effortless.
As developers, we've always considered traditional testing to be a pain point. We recall spending many hours building and maintaining test scripts that would fail even with small UI changes. We've always been frustrated by the disparity between how we naturally present our apps to others and how we have to create tests.
That is exactly why we created Iris. We wanted the testing to seem as natural as showing a colleague how your program works. There will be no more sophisticated test frameworks or brittle scripts; only intuitive, human-like testing that everybody on the team can comprehend.
We built it because we needed it, and we believe that many other devs have similar issues. Would love to hear your ideas and experiences with testing; what are your major pain points?
As a developer some times I needed to compromise parts of the engineering like tests in favor of speed. Love the fact that now I can write tests with natural
language, and also very fast. Looking forward to try it also on more complex apps
This is such a painful use case that it is difficult for many product managers and developers to solve, It solves a big pain point.
Are there any limitations on what it can help test? Or simply put what are the low hanging fruits (in terms of test use cases) where this can add value out of the box?
I recommend the Iris app as it makes it easy to test websites and apps to an incredible level. Thanks to its intuitive interface, there is no need to write complex code – just describe the tests in English and Iris will take care of the rest.
@ulysse_renaud We have it in roadmaps. We will be adding replication steps, context and even network and console errors.
You would get a screenshot/video and curls of apis.
Currently, we are not looking at load testing, what we do however have been working on is to identify slow queries while the ui testing is already under progress. Please let me know if you see us handing some other use cases as well. @danny_cartere
Looks promising. Another useful feature can be to auto generate integration test stubs for the test case so that the tests can be automated and integrated within CI/CD pipeline.
We currently support integration with github. The next part is to make sure we can read diffs and cache older test cases, so the system can be faster. Another part is automating backend testing which should in theory be relatively an easier job @aniket_sharma22
OpenCopilot