Tobias Müller
Yeah. So right now, TestResultsio was like, it's basically a completely different approach to identify elements, right? Because right now, what people often use or always use like to try to identify with which input do I need to intact? Where do I need to put my text, where do I need to select a value and they need to find try to identify a locator for that. That is wrong in every case. That is why TestResults just differently. And what we use because there is already a locator, there is something that you as a user tells you that just the right fit. If you see a field like a name, you know exactly that. And the next field should be my name and it's not the nearest field, by the way. It's it's a logically next field which is dependent on the culture that you were growing up with, stuff like that. And that is actually what you put into TestResultsio so it works completely different to any other system in the way of how it locates where it should interact. That's the first part. And then we do have the autonomous part where we are only partially out. So it's not fully autonomous testing. What we did is like? We trained the system to understand how like scrolling works. So if it doesn't find an element on the page or in the list, for example, where it can identify that there is a way to scroll. That there are myriad of ways to scroll, actually list, for example, that you cannot automate that by hand. We train the system on what the scrolling actually mean and how does that work? And what is the specifically on scrolling which can be at the top, you can be at the bottom already? You are not able to scroll at all, and they just want to be trained to system. And that is where we do have autonomous functionality in the system that you can just tell it like, hey, I want to go to that, I want to click that element, or I want to go to that page or something that in the system and show us that it could find that element if it's available. And that's a difference that we also do have a different approach to Gen AI, because what you see in Gen AI is always the typical approach. Is this like, hey, I do have my requirements, or I do have screenshots from my application generate test cases for that. And I also did test with somebody on LinkedIn and said, like, hey, I want to have test cases for WinWord. And then you always get those generic test cases likely the performance should be good. You should be able to log in. You should be able to not log in with your own credentials. It shouldn't allow you to log in without providing a username. So the typical test case is that everybody who is involved in testing can write down all of that. There's no real benefit. You're generating thousands of test cases without much benefit. What is the difference is like if you're generating this model of your application and then you're prompting use cases like for use ...... platform that that's my primary example. It's like you tell testers, I say, I want to buy a car. I want to buy an Aston Martin, for example, for $6,000. And that is what you put in the prompt. And based on the model that you generate in the background, it will actually generate the interactive steps. So you don't need to understand how your application works. You just give it a use case, and the system is already smart enough in most cases to identify what that sequence, and that is how you build up your testing. You test scenarios. That's how you build you user journeys because you don't talk about test cases anymore. We really think like, okay, what does the user want to achieve? And what are the steps to achieve that actually? And that is an auto generated step by step and that is a way of the context. So if you tell the system, hey, I would just like a test. It's a system for German parcel service and put in the information. I want to send the package to Japan and generates all of the steps. And I just said like, yeah. And by the way, it has let's say four kilograms, which is like how many pounds? 8 pounds? And it just added that at the right position in the chain of interactions. That is what we are doing different. So the claim is not okay, give us the requirements and we generate all of the test cases for you. Then we democratize the test generation. It's really like no, we do augmented stuff like give us a use case and we generate the steps for you because that's the nasty part, right? Nobody wants to drag and drop those elements and select the right inputs. I mean that's what it's exactly like for the execution. I mean, the intellectual part is coming up with a test scenario and with the use cases that you can actually change the system with, but not executing a test case or dragging and dropping those elements, keeping the data. And that's the difference in the TestResultsio.