All right, so this issue was created by me, I mean, I missed one of the one of the options to be
removed from the Perram.
So if you don't really specify the browser name, we need to also remove that problem from there.
So I'm just going to say with this guy and save this completely, probably also add the video option,
probably with the hyphen hyphen Perram.
And then I'm going to run this and see what's going to happen.
All right, you can see that the test has got fail, which is something we know already, so it's failing
because it says that the whole system is missing some dependencies and it is trying to install the missing
dependencies with these these these days.
But still, you can see that when it's time to execute someone, discard past six cards, skipped and
took out failed.
I think this is pretty much close to what happened in our Kitab actions as well.
So I think this is working fine.
I don't think that is not the unexpected results or this is expected result and it is working fine as
well.
So if I just go back to our GitHub actions once again, so if I go back here to the actual developes
and if I just read the pipeline
and if I just do a, uh, probably browser name is equal to chromium, and then I'm going to set the
video, uh, from Steph over here, not really concentrating anything on the comments and things.
I'm just running it regardless.
And you can see that the test has, in fact, got passed in this particular Azur Dope's pipeline, which
is quite good.
I mean, we didn't see this happen in the GitHub actions while we always try to get always used to get
errors.
But I think this is because this particular image, which is running the the normal is actually version
14.
If I'm not wrong.
No, it's to version 10.
That's what it says.
But still on 10, this is parsing, whereas on version 10 of a GitHub actions, it was actually failing
and it got passed on version number 14.
So this is quite interesting to see in different different secedes platforms.
This player is working pretty much different, which I'm not sure why.
Maybe that's because of the version issues or conflict, but looks like this guy is working fine and
it's quite good to see that this is working.
So you can try to add the artifacts in this one as well.
I just leave it to you now, see how you can grab the artifact and put it on the test results, get
it from the test results folder and put it on this particular artifact over here.
That's going to be pretty much exactly the same, like how we do it on the GitHub actions.
And that's it.
This is the way that we can integrate playwrite with Azure develops quite straightforward and quite
simple.
Not a big deal at all.