1 00:00:01,740 --> 00:00:08,220 All right, so this issue was created by me, I mean, I missed one of the one of the options to be 2 00:00:08,220 --> 00:00:09,240 removed from the Perram. 3 00:00:09,240 --> 00:00:13,040 So if you don't really specify the browser name, we need to also remove that problem from there. 4 00:00:13,350 --> 00:00:22,860 So I'm just going to say with this guy and save this completely, probably also add the video option, 5 00:00:23,220 --> 00:00:27,360 probably with the hyphen hyphen Perram. 6 00:00:27,630 --> 00:00:32,520 And then I'm going to run this and see what's going to happen. 7 00:00:41,770 --> 00:00:47,410 All right, you can see that the test has got fail, which is something we know already, so it's failing 8 00:00:47,410 --> 00:00:53,140 because it says that the whole system is missing some dependencies and it is trying to install the missing 9 00:00:53,140 --> 00:00:54,850 dependencies with these these these days. 10 00:00:55,390 --> 00:01:01,900 But still, you can see that when it's time to execute someone, discard past six cards, skipped and 11 00:01:01,900 --> 00:01:02,570 took out failed. 12 00:01:02,590 --> 00:01:07,030 I think this is pretty much close to what happened in our Kitab actions as well. 13 00:01:07,360 --> 00:01:09,330 So I think this is working fine. 14 00:01:09,340 --> 00:01:16,660 I don't think that is not the unexpected results or this is expected result and it is working fine as 15 00:01:16,660 --> 00:01:16,880 well. 16 00:01:17,200 --> 00:01:24,460 So if I just go back to our GitHub actions once again, so if I go back here to the actual developes 17 00:01:24,460 --> 00:01:27,160 and if I just read the pipeline 18 00:01:29,830 --> 00:01:40,030 and if I just do a, uh, probably browser name is equal to chromium, and then I'm going to set the 19 00:01:40,030 --> 00:01:47,980 video, uh, from Steph over here, not really concentrating anything on the comments and things. 20 00:01:47,980 --> 00:01:49,870 I'm just running it regardless. 21 00:01:58,330 --> 00:02:05,440 And you can see that the test has, in fact, got passed in this particular Azur Dope's pipeline, which 22 00:02:05,440 --> 00:02:06,130 is quite good. 23 00:02:06,130 --> 00:02:13,030 I mean, we didn't see this happen in the GitHub actions while we always try to get always used to get 24 00:02:13,030 --> 00:02:13,450 errors. 25 00:02:13,660 --> 00:02:21,790 But I think this is because this particular image, which is running the the normal is actually version 26 00:02:21,790 --> 00:02:22,270 14. 27 00:02:22,270 --> 00:02:22,980 If I'm not wrong. 28 00:02:23,110 --> 00:02:25,000 No, it's to version 10. 29 00:02:25,000 --> 00:02:25,960 That's what it says. 30 00:02:26,500 --> 00:02:31,720 But still on 10, this is parsing, whereas on version 10 of a GitHub actions, it was actually failing 31 00:02:31,930 --> 00:02:34,180 and it got passed on version number 14. 32 00:02:34,810 --> 00:02:39,640 So this is quite interesting to see in different different secedes platforms. 33 00:02:39,910 --> 00:02:43,870 This player is working pretty much different, which I'm not sure why. 34 00:02:43,870 --> 00:02:49,450 Maybe that's because of the version issues or conflict, but looks like this guy is working fine and 35 00:02:49,460 --> 00:02:51,880 it's quite good to see that this is working. 36 00:02:52,330 --> 00:02:55,290 So you can try to add the artifacts in this one as well. 37 00:02:55,300 --> 00:03:01,300 I just leave it to you now, see how you can grab the artifact and put it on the test results, get 38 00:03:01,300 --> 00:03:04,500 it from the test results folder and put it on this particular artifact over here. 39 00:03:04,750 --> 00:03:07,690 That's going to be pretty much exactly the same, like how we do it on the GitHub actions. 40 00:03:08,050 --> 00:03:08,870 And that's it. 41 00:03:08,890 --> 00:03:14,200 This is the way that we can integrate playwrite with Azure develops quite straightforward and quite 42 00:03:14,200 --> 00:03:14,600 simple. 43 00:03:14,950 --> 00:03:15,850 Not a big deal at all.