WEBVTT 1 00:00:00.040 --> 00:00:03.319 All right, time to really get into web Driver EO. 2 00:00:03.759 --> 00:00:05.480 I know you guys are super interested in this. 3 00:00:05.639 --> 00:00:09.160 Oh yeah, definitely. This is like the framework everyone's talking. 4 00:00:08.960 --> 00:00:11.839 About right now, and for a good reason, right, totally totally. 5 00:00:11.919 --> 00:00:14.519 Yeah. So, you know, maybe you're starting a new project, 6 00:00:14.599 --> 00:00:16.320 or maybe you just want to be in the no 7 00:00:16.719 --> 00:00:19.640 whatever it is. You sent in a really cool excerpt 8 00:00:19.640 --> 00:00:23.679 to kick things off, practical web Driver EO. Nice choice. 9 00:00:23.800 --> 00:00:25.480 Yeah, that's a great book, and we have. 10 00:00:25.480 --> 00:00:27.320 Our expert here to break it all down, you know, 11 00:00:27.640 --> 00:00:29.239 especially all the technical stuff. 12 00:00:29.000 --> 00:00:31.559 So absolutely happy to help make sense of it all perfect. 13 00:00:31.760 --> 00:00:36.920 So web DRIVERYO. It's not just another framework, right. It's 14 00:00:36.960 --> 00:00:40.799 built on no JS, right, which basically means like it 15 00:00:40.880 --> 00:00:42.119 s beaks JavaScript like. 16 00:00:42.079 --> 00:00:44.679 A native Yeah, it's perfect if your application is already 17 00:00:44.759 --> 00:00:46.479 using a lot of javascripts exactly. 18 00:00:47.079 --> 00:00:51.520 Okay, But like the big question, why would someone choose 19 00:00:51.520 --> 00:00:56.119 web Driver EO over say, Selenium or even Cyprus. 20 00:00:56.439 --> 00:00:58.920 Oh that's a great question, and that's where the practical 21 00:00:59.000 --> 00:01:01.880 in your source really comes in. You know, Webdriver YO 22 00:01:02.039 --> 00:01:05.680 is known for being super flexible. Sometimes Selenium it can 23 00:01:05.719 --> 00:01:09.359 feel a little bit rigid, Okay, yeah, especially if you're 24 00:01:09.359 --> 00:01:12.599 working with like elements on a web page that change 25 00:01:12.640 --> 00:01:15.079 a lot, or you need to do some really complex 26 00:01:15.120 --> 00:01:18.760 stuff right right, webdriver Yo gives you a lot more control. 27 00:01:19.040 --> 00:01:21.400 I see, I see. And in the source they talk 28 00:01:21.480 --> 00:01:25.519 about the package dot Jason file pretty early on. Yeah, 29 00:01:25.680 --> 00:01:30.079 which you know, any no JS developer knows that file 30 00:01:30.280 --> 00:01:32.079 like the back of their hand for sure. But the 31 00:01:32.159 --> 00:01:35.560 cool thing is the book doesn't like dwell on the basics. 32 00:01:35.760 --> 00:01:37.599 It jumps right into the stuff that can be a 33 00:01:37.640 --> 00:01:41.719 real headache, you know, like managing all those dependencies, Oh absolutely, 34 00:01:41.760 --> 00:01:43.879 and especially making sure all the versions play nice with 35 00:01:43.959 --> 00:01:46.000 each other, which oh boy. 36 00:01:45.959 --> 00:01:47.599 Yeah version mismatches a node. 37 00:01:47.640 --> 00:01:49.439 I mean, don't even get me started. 38 00:01:49.599 --> 00:01:50.400 It's a whole thing. 39 00:01:50.480 --> 00:01:52.719 The author definitely seems to know where people will get 40 00:01:52.719 --> 00:01:53.200 tripped up. 41 00:01:53.239 --> 00:01:54.560 It's like it's like they've been there. 42 00:01:54.879 --> 00:01:58.599 Yeah, exactly, like they've seen it all. So the source 43 00:01:59.159 --> 00:02:02.719 it suggests like some proactive stuff you can do, like 44 00:02:03.120 --> 00:02:07.120 using a lock file to basically freeze those dependencies. Yeah, 45 00:02:07.239 --> 00:02:10.319 and also just like updating regularly so you don't fall too. 46 00:02:10.280 --> 00:02:12.280 Far back for sure, keep things fresh, you know. 47 00:02:12.520 --> 00:02:15.840 Yeah. Absolutely. Have you ever had like a full on 48 00:02:15.960 --> 00:02:17.120 dependency nightmare? 49 00:02:17.199 --> 00:02:19.759 Oh? Yeah, absolutely? I mean who hasn't spent hours and 50 00:02:19.840 --> 00:02:22.080 hours debugging just to realize, oh it's. 51 00:02:21.960 --> 00:02:26.479 Some tiny little version contact. Yeah it's the worst. But okay, 52 00:02:27.000 --> 00:02:30.560 enough about setup woes. What really caught my eye in 53 00:02:30.599 --> 00:02:35.759 this source was like this amazing section on locator strategies. 54 00:02:36.039 --> 00:02:38.879 Oh yeah, it's like a masterclass in how to find 55 00:02:38.919 --> 00:02:40.759 exactly what you need on a web page. 56 00:02:41.000 --> 00:02:44.360 Locators. That's the foundation of any good automation framework. And 57 00:02:44.400 --> 00:02:46.919 the source it goes into like all these different types, 58 00:02:47.039 --> 00:02:50.800 is it the ton I, DCSs, selectors, X path, even 59 00:02:50.879 --> 00:02:52.039 just planelink text. 60 00:02:52.159 --> 00:02:53.120 It's pretty impressive. 61 00:02:53.439 --> 00:02:55.960 But it's not just knowing they exist, right, it's about 62 00:02:56.039 --> 00:02:57.159 choosing the right one. 63 00:02:57.280 --> 00:02:59.199 Oh, that's where the strategy comes in. Yes, The source 64 00:02:59.240 --> 00:03:02.800 talks about finding the most reliable locator, you know, like 65 00:03:03.039 --> 00:03:05.280 if you have a logo and it has a unique ID. 66 00:03:05.520 --> 00:03:07.719 Yeah, Like, if it's a static ID, go for it, 67 00:03:08.039 --> 00:03:09.199 use that exactly. 68 00:03:09.400 --> 00:03:11.919 That's probably your best bet. But if you have stuff 69 00:03:11.919 --> 00:03:14.439 on the page that's always changing. 70 00:03:14.240 --> 00:03:16.680 Oh, dynamically generated concept. 71 00:03:16.240 --> 00:03:18.719 Yeah, that's when things get a little bit tricky. Totally. 72 00:03:19.159 --> 00:03:22.560 The source it says like IDs should be your go 73 00:03:22.639 --> 00:03:25.599 to whenever you can, because they tend to be the 74 00:03:25.599 --> 00:03:28.439 most stable. Okay, makes sense, But when you're dealing with 75 00:03:28.520 --> 00:03:31.599 more complex stuff CSS selectors they can give you a 76 00:03:31.599 --> 00:03:35.599 lot more flexibility. XPath can be super powerful. But it's 77 00:03:35.639 --> 00:03:39.159 also like if the structure of the web page changes, 78 00:03:39.240 --> 00:03:40.360 it can break your. 79 00:03:40.199 --> 00:03:43.120 Tests right right, it's more fragile exactly. It's almost like 80 00:03:43.159 --> 00:03:45.599 you need to be a detective, you know, looking at 81 00:03:45.599 --> 00:03:48.680 the web page's HTML, like searching for clues. That's a 82 00:03:48.680 --> 00:03:51.319 great analogy, trying to find that perfect locator. 83 00:03:51.360 --> 00:03:53.960 It's and the source it even gives you tips on 84 00:03:54.159 --> 00:03:58.280 using your browsers, developer tools, you know, to inspect elements 85 00:03:58.319 --> 00:04:02.000 and test out different locators. Yeah, it encourages you to experiment, 86 00:04:02.000 --> 00:04:03.759 get your hands dirty, which I really like. 87 00:04:03.879 --> 00:04:07.400 Yeah totally. So, okay, we've got our elements, they're all 88 00:04:07.439 --> 00:04:10.360 locked down, Now what can we actually de with them? 89 00:04:10.439 --> 00:04:12.000 That's where the fun begins, right. 90 00:04:12.120 --> 00:04:15.080 This source goes deep, deep into this amazing world of 91 00:04:15.120 --> 00:04:15.960 browser commands. 92 00:04:16.040 --> 00:04:17.920 Oh yeah, it's like having superpowers. 93 00:04:18.040 --> 00:04:22.360 It really is. Like switching between windows, no problem, piece 94 00:04:22.399 --> 00:04:25.519 of cake, Taking screenshots of the entire page, like the 95 00:04:25.560 --> 00:04:28.600 whole layout, easy psy and get this. You can even 96 00:04:28.639 --> 00:04:32.759 inject JavaScript for those moments when you'd need ultimate control. 97 00:04:33.600 --> 00:04:35.199 That's where things get really interesting. 98 00:04:35.360 --> 00:04:38.639 For example, you know, you imagine you have a website 99 00:04:38.920 --> 00:04:41.120 and you have users all over the world. 100 00:04:41.120 --> 00:04:42.639 Oh yeah, international users. 101 00:04:42.720 --> 00:04:46.120 The source it gives an example of how to simulate geolocation. 102 00:04:46.399 --> 00:04:48.639 Oh wow, so you can see how the site behaves 103 00:04:48.639 --> 00:04:52.279 if you were in like I don't know the rebuta triangle. 104 00:04:52.319 --> 00:04:53.040 That's pretty cool. 105 00:04:53.120 --> 00:04:55.959 Maybe not the best place for vacation, but you get 106 00:04:55.959 --> 00:04:56.480 the idea. 107 00:04:56.680 --> 00:04:58.800 Yeah, I get it. So that's what makes webdriver yos 108 00:04:58.839 --> 00:04:59.319 so awesome. 109 00:04:59.439 --> 00:05:00.399 It really is powerful. 110 00:05:00.639 --> 00:05:03.959 It's not just about like clicking buttons or filling in forms. 111 00:05:04.040 --> 00:05:09.680 It's about recreating real world scenarios like location based services. 112 00:05:09.199 --> 00:05:12.319 And stuff exactly. And the source it doesn't just tell 113 00:05:12.360 --> 00:05:15.120 you like, hey, here's this cool feature, right, it tells 114 00:05:15.120 --> 00:05:16.879 you why it matters. 115 00:05:16.639 --> 00:05:17.399 Yeah the way. 116 00:05:17.439 --> 00:05:21.600 So like simulating geolocation, it's not just a neat trick. 117 00:05:22.519 --> 00:05:26.360 It's actually super important for testing features. You know, like 118 00:05:26.560 --> 00:05:31.360 if you have location based search, targeted content, even stuff 119 00:05:31.360 --> 00:05:32.920 like delivery services. 120 00:05:32.519 --> 00:05:33.319 You know makes sense. 121 00:05:33.720 --> 00:05:35.800 It adds a whole new dimension to how you think 122 00:05:35.800 --> 00:05:36.439 about testing. 123 00:05:36.560 --> 00:05:38.160 It's about thinking outside the box. 124 00:05:38.279 --> 00:05:40.839 Yeah, totally, okay, so we can find elements we can 125 00:05:40.879 --> 00:05:43.240 interact with them, but what about making sure they actually 126 00:05:43.240 --> 00:05:44.319 work the way they're supposed to go. 127 00:05:44.360 --> 00:05:46.480 Oh, that's where assertions come in, right, exactly. 128 00:05:46.759 --> 00:05:48.879 And this source goes deep into the world of web 129 00:05:48.959 --> 00:05:50.079 drive reo assertions. 130 00:05:50.120 --> 00:05:52.399 They're like checkpoints for your application. 131 00:05:52.560 --> 00:05:55.279 Yeah, exactly. So it's not enough to just like poke 132 00:05:55.319 --> 00:05:57.279 around and see if things kind of work right. You 133 00:05:57.399 --> 00:06:00.399 got to be specific, like this element must do this. 134 00:06:00.399 --> 00:06:02.879 Yeah, and then you check if that's actually true. 135 00:06:03.040 --> 00:06:06.759 Yeah. And this source it goes way beyond the basics, 136 00:06:06.800 --> 00:06:09.879 Like there are all these specialized assertions that webdriver Yo 137 00:06:09.959 --> 00:06:10.240 give you. 138 00:06:10.319 --> 00:06:12.160 Oh it's awesome, right, it's like going from a basic 139 00:06:12.240 --> 00:06:14.839 checkup to a full blown medical scam. 140 00:06:15.040 --> 00:06:18.240 Love that analogy. So the source it starts with this 141 00:06:18.279 --> 00:06:21.279 assertion is existing. Oh yeah, I no, it checks if 142 00:06:21.319 --> 00:06:24.600 an element is actually there, you know, in the dom. 143 00:06:24.600 --> 00:06:27.720 But here's the thing, and the source points this out. Yeah, 144 00:06:27.720 --> 00:06:31.800 it's subtle, is existing. It won't actually fail your test 145 00:06:32.160 --> 00:06:33.319 if the element's missing. 146 00:06:33.839 --> 00:06:35.759 Right. It's more about gathering information. 147 00:06:36.000 --> 00:06:36.839 So it's like a scalp. 148 00:06:37.000 --> 00:06:38.079 Yeah, like a little spy. 149 00:06:38.279 --> 00:06:42.040 Hey this element there, Yep, it's there, or Nope, can't 150 00:06:42.040 --> 00:06:42.560 find it. 151 00:06:43.000 --> 00:06:44.839 And then you decide what to do with that. 152 00:06:44.839 --> 00:06:47.720 Information exactly exactly. Maybe you want to wait for it 153 00:06:47.759 --> 00:06:49.560 to show up, or maybe you want to handle it 154 00:06:49.600 --> 00:06:50.680 gracefully if it's not there. 155 00:06:50.759 --> 00:06:53.519 Right, It's all about flexibility and being in control, you know. 156 00:06:53.639 --> 00:06:57.959 Totally totally, And if you do want an assertion that's like, hey, 157 00:06:58.040 --> 00:07:01.240 this element better be here or we have a problem. 158 00:07:01.399 --> 00:07:02.519 Yeah, like a hard stop. 159 00:07:02.759 --> 00:07:06.759 Yeah, the source recommends to exist or to be present. 160 00:07:07.319 --> 00:07:08.639 Those are your go to for sure. 161 00:07:08.720 --> 00:07:13.600 Okay, what about elements that are there but they're like hiding. 162 00:07:13.360 --> 00:07:14.480 Oh you mean visible? Yeah? 163 00:07:14.560 --> 00:07:18.839 Yeah, visibility. As users we take it for granted totally, 164 00:07:18.879 --> 00:07:21.279 but an automation, huge. 165 00:07:21.000 --> 00:07:25.360 Deal huge, So that's where you use is displayed. It's 166 00:07:25.360 --> 00:07:28.360 like saying, hey, not only should this element be there, 167 00:07:28.399 --> 00:07:31.120 but it should be visible too, like a user could 168 00:07:31.120 --> 00:07:34.160 actually see it makes sense, And just like before, you've 169 00:07:34.160 --> 00:07:37.839 got a stronger version to be displayed or too visible. 170 00:07:37.959 --> 00:07:38.519 Oh I like that. 171 00:07:38.600 --> 00:07:41.040 Yeah, if you need to be absolutely sure. 172 00:07:40.879 --> 00:07:43.319 Yeah totally. Oh and the source even talks about this 173 00:07:43.639 --> 00:07:46.319 cool assertion to be visible in viewport. 174 00:07:46.560 --> 00:07:48.040 Oh yeah that's a good one. 175 00:07:48.079 --> 00:07:50.079 This one's like next level thing. 176 00:07:50.319 --> 00:07:52.480 He checks if the element's not just visible, but if 177 00:07:52.480 --> 00:07:54.399 it's actually in the part of the page the user 178 00:07:54.439 --> 00:07:55.759 can see without scrawling right. 179 00:07:55.680 --> 00:07:57.680 Right, because you could have a super long web page. 180 00:07:57.879 --> 00:08:00.360 Yeah, and technically an element could be visible, but if 181 00:08:00.360 --> 00:08:02.399 you've got to scroll down a mile to find it, 182 00:08:02.480 --> 00:08:04.319 is it really visible exactly? 183 00:08:04.399 --> 00:08:06.360 It's like you got to think like a user, you know, 184 00:08:06.800 --> 00:08:09.720 how are they actually experiencing thisally? Totally? Okay, So we've 185 00:08:09.720 --> 00:08:13.759 got presence, we've got visibility. What about elements that are 186 00:08:13.879 --> 00:08:17.920 visible but you can't like interact with them, like a 187 00:08:17.920 --> 00:08:19.480 button that's disabled or something. 188 00:08:19.560 --> 00:08:21.199 Yeah, that's a good one. So the source it goes 189 00:08:21.199 --> 00:08:23.959 into that too. You can check if an element is 190 00:08:24.079 --> 00:08:27.319 enabled or disabled using like to be enabled and to 191 00:08:27.360 --> 00:08:28.040 be disabled. 192 00:08:28.079 --> 00:08:30.439 Ah okay, so you're making sure those interactive elements are 193 00:08:30.480 --> 00:08:32.799 actually like working exactly. 194 00:08:32.960 --> 00:08:35.759 And checkboxes, Oh, don't get me started on checkboxes. 195 00:08:35.799 --> 00:08:37.240 It can be a real pain to test. 196 00:08:37.440 --> 00:08:42.120 The source it highlights is selected and to be selected. 197 00:08:42.720 --> 00:08:45.360 Use those to check if a checkboxes you know, checked 198 00:08:45.440 --> 00:08:48.879 or not. Right might seem small, but it's important. Like 199 00:08:48.919 --> 00:08:51.480 think about accepting terms and conditions on a website. 200 00:08:51.600 --> 00:08:53.919 Yeah, if that checkbox isn't checked, you might not be 201 00:08:53.960 --> 00:08:55.360 able to do anything exactly. 202 00:08:55.720 --> 00:08:58.759 It's those little things that can make or break the 203 00:08:58.840 --> 00:09:00.879 whole user experience, and. 204 00:09:00.840 --> 00:09:03.679 Web Driver EO gives you the power to test all 205 00:09:03.720 --> 00:09:04.279 of it. 206 00:09:04.279 --> 00:09:06.639 It does, yeah, and you know it's cool the source. 207 00:09:06.720 --> 00:09:09.440 It goes beyond just listing assertions. It actually gives you 208 00:09:09.559 --> 00:09:13.320 a whole example of like a real world test case. 209 00:09:13.759 --> 00:09:16.480 Oh nice, yeah, for a user loginflow, so. 210 00:09:16.440 --> 00:09:18.600 You can see everything in action exactly. 211 00:09:18.720 --> 00:09:21.279 You see how web driver EYO can do like end 212 00:09:21.320 --> 00:09:23.919 to end testing, not just little isolated checks. 213 00:09:24.120 --> 00:09:27.159 I love that. And it uses like the Page Object 214 00:09:27.200 --> 00:09:30.240 Model POM to keep everything organized, right m h. 215 00:09:30.639 --> 00:09:31.840 POMM is the way to go. 216 00:09:31.960 --> 00:09:34.279 So it starts by like making sure all the important 217 00:09:34.320 --> 00:09:37.000 elements are there, like the logo, the input fields, you know, 218 00:09:37.120 --> 00:09:39.120 all that good stuff, and then it makes sure they're 219 00:09:39.200 --> 00:09:40.320 visible and enabled. 220 00:09:40.519 --> 00:09:42.919 Yeah, got to make sure they're ready for action exactly. 221 00:09:43.120 --> 00:09:45.360 Then it's like, okay, let's simulate a user typing in 222 00:09:45.399 --> 00:09:47.799 their username and password. And here's what I really like 223 00:09:47.840 --> 00:09:50.919 about it. It doesn't just assume everything's going to work perfectly. 224 00:09:51.039 --> 00:09:52.320 Oh yeah, that's key. 225 00:09:52.399 --> 00:09:56.600 It uses those conditional statements if and else right, so 226 00:09:56.639 --> 00:09:58.919 it can handle like if an element is missing or 227 00:09:58.960 --> 00:10:02.600 if it's disabled. It and like log a warning or something. 228 00:10:02.639 --> 00:10:05.480 Yeah, instead of just crashing the whole test exactly. 229 00:10:05.799 --> 00:10:08.320 So it's like built in resilience. Yeah, you know, not 230 00:10:08.399 --> 00:10:10.720 every cast needs to be a straight up pass or fail. 231 00:10:10.840 --> 00:10:12.720 Sometimes you just want to know, like, hey, what could 232 00:10:12.759 --> 00:10:13.399 go wrong here? 233 00:10:13.600 --> 00:10:17.759 Exactly. It's about finding that sweet spot between being thorough 234 00:10:17.960 --> 00:10:19.519 and also being realistic, you know. 235 00:10:19.600 --> 00:10:21.679 And the source does a great job of showing you 236 00:10:21.679 --> 00:10:22.159 how to do that. 237 00:10:22.279 --> 00:10:26.320 Yeah, it really does. So all this talk about assertions, 238 00:10:26.399 --> 00:10:29.200 it brings up another super important part of web Drive 239 00:10:29.279 --> 00:10:29.919 REO testing. 240 00:10:30.399 --> 00:10:30.759 Waits. 241 00:10:31.159 --> 00:10:35.120 Oh yeah, waits essential. The source dedicates a good Yeah. Basically, 242 00:10:35.120 --> 00:10:37.279 you just pause the test for a certain amount of time. 243 00:10:37.440 --> 00:10:39.480 You have the application a chance to catch up. 244 00:10:39.679 --> 00:10:42.440 It's like saying, okay, everyone, take a deep breath, count 245 00:10:42.480 --> 00:10:44.960 to ten and then we'll continue. I like that, but 246 00:10:45.039 --> 00:10:48.440 for more dynamic situations, you need something a little smarter, right. 247 00:10:48.440 --> 00:10:50.080 Yeah, Like wait for display. 248 00:10:50.159 --> 00:10:51.720 Oh yeah, that one's super useful. 249 00:10:51.919 --> 00:10:54.960 It waits for an element to actually become visible on 250 00:10:55.080 --> 00:10:55.639 the page. 251 00:10:55.840 --> 00:10:58.799 So you're not just waiting for an arbitrary amount of time, right, 252 00:10:59.000 --> 00:11:00.919 You're waiting for a special thing to happen. 253 00:11:01.200 --> 00:11:05.159 That's where you see web Driver EOS flexibility and action. 254 00:11:05.279 --> 00:11:08.080 And the cool thing is you can customize the time 255 00:11:08.120 --> 00:11:10.919 out period so you can control how long you're willing 256 00:11:10.960 --> 00:11:13.840 to wait, you know, and the polling interval, like how 257 00:11:13.879 --> 00:11:16.159 often it checks to see if the condition's been met. 258 00:11:16.240 --> 00:11:19.320 It's like fine tuning your patience level exactly exactly. 259 00:11:19.600 --> 00:11:21.919 And then you've got weight for enabled that waits for 260 00:11:21.960 --> 00:11:24.480 an element to become enabled so you can actually interact 261 00:11:24.519 --> 00:11:24.799 with it. 262 00:11:24.919 --> 00:11:27.000 Yeah, like a button that's initially grayed out. 263 00:11:27.200 --> 00:11:30.840 Yeah know, at wait for exist. No one waits for 264 00:11:30.879 --> 00:11:33.759 an element to like actually exist in the dom. 265 00:11:33.879 --> 00:11:36.360 Web driver eyo gives you all the tools to handle 266 00:11:36.399 --> 00:11:38.720 those tricky asynchronous operations. 267 00:11:39.000 --> 00:11:43.279 It does, but the real star of the show when 268 00:11:43.279 --> 00:11:46.679 it comes to waits is wait until. 269 00:11:46.440 --> 00:11:48.600 Oh yeah, wait until. That's the big one. 270 00:11:48.639 --> 00:11:52.200 This one's like ultimate flexibility. It's like a magic wand 271 00:11:52.320 --> 00:11:54.120 you can define your own custom condition. 272 00:11:54.559 --> 00:11:57.360 The source it gives a great example of using it 273 00:11:57.440 --> 00:12:00.720 to wait for an element to have specific tech content. 274 00:12:00.919 --> 00:12:02.799 Oh super powerful. 275 00:12:02.360 --> 00:12:05.960 So like you're not limited to just the pre defined conditions, right, 276 00:12:06.600 --> 00:12:08.080 you can get as creative as you need to be. 277 00:12:08.200 --> 00:12:11.320 It's all about tailoring your weights to your specific. 278 00:12:10.759 --> 00:12:14.080 Needs totally, and you still have control, like you can 279 00:12:14.120 --> 00:12:16.440 set a time out, you can set a custom message 280 00:12:16.440 --> 00:12:18.440 if it times out. You can even control how often 281 00:12:18.480 --> 00:12:19.519 it checks for the condition. 282 00:12:19.960 --> 00:12:21.000 Super customizable. 283 00:12:21.120 --> 00:12:24.600 Okay, so weights, they're absolutely crucial, and this source does 284 00:12:24.600 --> 00:12:27.679 a fantastic job of explaining like all the ins and 285 00:12:27.720 --> 00:12:30.279 outs it does. Now, let's talk frameworks. We touched on 286 00:12:30.279 --> 00:12:33.440 them briefly before, but this source it really gets into 287 00:12:33.440 --> 00:12:35.759 the specifics of Cucumber and Typescript. 288 00:12:36.120 --> 00:12:39.159 Yeah, frameworks they bring structure to your test code, you know, 289 00:12:39.200 --> 00:12:42.120 they help you organize everything right, and the source it 290 00:12:42.200 --> 00:12:44.000 highlights the benefits of each one. 291 00:12:44.120 --> 00:12:45.480 Yeah, it does a great job of that. 292 00:12:45.799 --> 00:12:50.200 So Cucumber it's all about that behavior driven development approach, 293 00:12:50.320 --> 00:12:54.039 you know BDD. It's perfect for teams that really want 294 00:12:54.080 --> 00:12:56.440 to collaborate and they want to make sure their tests 295 00:12:56.480 --> 00:13:00.440 are understandable to like everyone involved, not just the developers. 296 00:13:00.480 --> 00:13:02.879 Yeah, it's like bridging that gap between the technical folks 297 00:13:02.879 --> 00:13:05.519 and the you know, the non technical folks exactly. And 298 00:13:05.559 --> 00:13:09.000 then you've got Typescript, which brings that like lovely type 299 00:13:09.039 --> 00:13:11.080 safety to the JavaScript world. 300 00:13:11.120 --> 00:13:14.200 Oh yeah, Typescript is a life savers, especially when you're 301 00:13:14.200 --> 00:13:16.480 working on a big, complex project. 302 00:13:16.600 --> 00:13:20.399 It can really help catch errors early on. Absolutely, so 303 00:13:20.440 --> 00:13:22.879 it really comes down to like what does your team need, 304 00:13:23.440 --> 00:13:24.519 what are your preferences. 305 00:13:24.720 --> 00:13:27.559 It's all about finding the right tools for the job totally. 306 00:13:28.039 --> 00:13:30.759 And the source it even walks you through how to 307 00:13:30.840 --> 00:13:34.879 set up both frameworks with webdriveryo like step by step. 308 00:13:35.000 --> 00:13:36.200 Yeah, it's super helpful. 309 00:13:36.440 --> 00:13:39.679 Okay, before we move on to the really fun stuff. Yeah, 310 00:13:39.720 --> 00:13:41.120 actually writing the test scripts. 311 00:13:41.240 --> 00:13:42.840 I know I'm excited for that, me too. 312 00:13:43.480 --> 00:13:47.679 But first let's talk about the configuration file wato dot 313 00:13:47.720 --> 00:13:48.559 com dot js. 314 00:13:48.879 --> 00:13:50.399 Oh yeah, the control center. 315 00:13:50.480 --> 00:13:53.399 It's like mission control for your webdriver real project. 316 00:13:54.600 --> 00:13:57.639 And the source. It gives a great overview of all 317 00:13:57.679 --> 00:14:02.240 the different configuration options there, from logging levels and services 318 00:14:02.240 --> 00:14:04.720 to reporters and capabilities. It's all there. 319 00:14:04.919 --> 00:14:08.720 It's pretty impressive. And the source it really emphasizes like 320 00:14:08.759 --> 00:14:11.559 you got to understand what each option does you know, like, 321 00:14:11.600 --> 00:14:13.200 how does it actually affect your tests? 322 00:14:13.279 --> 00:14:15.639 Yeah, it's about making informed choices exactly. 323 00:14:15.679 --> 00:14:17.720 Don't just copy and paste stuff without knowing what it's 324 00:14:17.720 --> 00:14:18.320 doing exactly. 325 00:14:18.360 --> 00:14:20.240 Got to understand the why behind the what. 326 00:14:20.759 --> 00:14:22.960 And the source it does a great job of explaining 327 00:14:22.960 --> 00:14:23.679 all those whys. 328 00:14:23.919 --> 00:14:25.799 It's like having a personalized setup guide. 329 00:14:25.799 --> 00:14:33.080 You know, totally, totally. So we've covered installation, locators, commands, assertions, frameworks, configuration. Wow, 330 00:14:33.120 --> 00:14:36.159 that's a lot, I know, right, Yeah, it's incredible how 331 00:14:36.240 --> 00:14:39.000 much this source manages to pack into like a short excerpt. 332 00:14:39.200 --> 00:14:41.720 It's a good foundation though, it is, and I think 333 00:14:41.799 --> 00:14:44.080 it sets us up perfectly to actually start writing those 334 00:14:44.120 --> 00:14:44.720 test scripts. 335 00:14:44.840 --> 00:14:47.639 Yeah, which is what we'll be diving into next time exactly. 336 00:14:48.279 --> 00:14:50.919 But before we jump into all that practical stuff, let's 337 00:14:51.000 --> 00:14:53.320 just pause for a minute and let everything we've talked 338 00:14:53.360 --> 00:14:54.960 about today sink in. 339 00:14:55.279 --> 00:14:56.759 You know, yeah, take a breath there. 340 00:14:56.840 --> 00:14:58.799 It's a lot, but it's exciting it is. 341 00:14:59.000 --> 00:15:02.039 And with this found foundation, I mean, you guys are 342 00:15:02.039 --> 00:15:04.720 well on your way to becoming web driver EO masters. 343 00:15:05.000 --> 00:15:08.759 That's the goal, and building super robust and reliable tests 344 00:15:08.799 --> 00:15:11.360 for your applications, whatever those applications might be. 345 00:15:11.679 --> 00:15:14.639 That's the dream, right, all right, welcome back to our 346 00:15:14.679 --> 00:15:16.200 web driver Yo, deep dive. 347 00:15:16.360 --> 00:15:17.919 I'm excited for this part, me too. 348 00:15:18.639 --> 00:15:23.879 Last time we laid down all the groundwork, like installation locators, commands, 349 00:15:24.360 --> 00:15:26.279 all the essential there's like getting a sneak peek into 350 00:15:26.320 --> 00:15:29.360 the frameworks toolkit, right, but now it's time to see 351 00:15:29.399 --> 00:15:31.200 how those tools actually work in practice. 352 00:15:31.360 --> 00:15:32.320 Let's get hands on. 353 00:15:32.600 --> 00:15:36.919 Exactly and this source practical web Driver. Yo, it's a 354 00:15:36.960 --> 00:15:39.679 perfect guide for this part of the journey. It doesn't 355 00:15:39.679 --> 00:15:41.799 just tell you what to do, it shows you how 356 00:15:41.799 --> 00:15:44.000 to do it right the right way. Yeah, like how 357 00:15:44.039 --> 00:15:46.919 to write test scripts that are clean, easy to maintain, 358 00:15:47.000 --> 00:15:50.679 and super reliable. That's what we want exactly. So the 359 00:15:50.759 --> 00:15:53.840 source it starts off with this design pattern that's like 360 00:15:54.000 --> 00:15:57.559 super popular in the testing world, the Page Object model 361 00:15:57.919 --> 00:15:58.799 or POM. 362 00:15:58.960 --> 00:16:00.320 Oh yeah, POM got love. 363 00:16:00.879 --> 00:16:03.279 I've heard people talk about it, but honestly, this source 364 00:16:03.360 --> 00:16:04.480 finally made it click for me. 365 00:16:04.799 --> 00:16:06.840 Yeah. POM can be a game changer for sure. 366 00:16:06.919 --> 00:16:10.000 It's all about bringing order to the chaos, right, Like 367 00:16:10.360 --> 00:16:13.559 thinking of your application is a collection of pages, and 368 00:16:13.679 --> 00:16:17.639 each page has its own like unique elements and interactions. 369 00:16:17.799 --> 00:16:20.120 Right And instead of having your test code all over 370 00:16:20.159 --> 00:16:24.000 the place, you create separate classes for each page. Ah, 371 00:16:24.240 --> 00:16:26.639 so you can keep everything organized and easy to find. 372 00:16:26.720 --> 00:16:30.000 It's like creating a blueprint for each page exactly. So, Like, 373 00:16:30.159 --> 00:16:31.799 if you have a log in page, you'd have a 374 00:16:31.799 --> 00:16:34.159 log in page class. Yeah, and that class would have 375 00:16:34.200 --> 00:16:37.919 all the locators for like the username field, the password field, 376 00:16:37.960 --> 00:16:39.080 the log in button. 377 00:16:39.440 --> 00:16:42.799 And the methods for actually interacting with those elements too. 378 00:16:42.960 --> 00:16:46.720 Ah okay, okay, so instead of having like this cryptic 379 00:16:46.799 --> 00:16:49.000 code all over your test scripts, you'd have these nice, 380 00:16:49.080 --> 00:16:50.960 clean method calls right exactly. 381 00:16:51.000 --> 00:16:53.080 It makes your code so much more readable. 382 00:16:53.159 --> 00:16:56.480 It's like writing a story, yeah, about how your tests 383 00:16:56.480 --> 00:16:57.879 are interacting with the application. 384 00:16:58.080 --> 00:17:00.799 And if the layout of the page changes, you only 385 00:17:00.840 --> 00:17:05.279 need to update the page object class. Oh, you don't 386 00:17:05.319 --> 00:17:06.839 have to touch all your test scripts. 387 00:17:06.920 --> 00:17:08.799 That makes updating so much easier. 388 00:17:08.519 --> 00:17:12.000 Exactly, makes your code less fragile, less likely to break 389 00:17:12.160 --> 00:17:13.480 when things change, and. 390 00:17:13.440 --> 00:17:17.720 The source it actually walks you through an example of implementing. 391 00:17:17.319 --> 00:17:21.960 POM, Yeah, step by step surprisingly straightforward. It is. Yeah, 392 00:17:22.000 --> 00:17:25.079 you create a folder for your page objects, and then 393 00:17:25.119 --> 00:17:27.599 you define a class for each page okay, with all 394 00:17:27.640 --> 00:17:29.960 your locators and your methods nice and organized. 395 00:17:30.119 --> 00:17:33.000 I love it. It's like building a library of reusable 396 00:17:33.000 --> 00:17:34.519 components for your tests. 397 00:17:34.480 --> 00:17:37.799 Exactly, And as your application grows, your library grows with it. 398 00:17:38.039 --> 00:17:44.079 Awesome. Okay, so POM is definitely a game changer. What 399 00:17:44.519 --> 00:17:49.000 other like golden nuggets of wisdom does this source have 400 00:17:49.119 --> 00:17:51.440 about writing really good test scripts? 401 00:17:51.640 --> 00:17:53.559