All language subtitles for 394 Finding widgets and matcher arguments.en

af Afrikaans
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,420 --> 00:00:05,740 Now that we have managed to load a custom raised button with the pump we did mattered. 2 00:00:05,820 --> 00:00:08,260 We can start doing something interesting with it. 3 00:00:08,260 --> 00:00:14,610 And for example we could check that this widget has a raised button inside it and to do that we need 4 00:00:14,610 --> 00:00:17,390 to use an object which is called a finder. 5 00:00:17,430 --> 00:00:23,010 So over here we can type the final button equals find. 6 00:00:23,130 --> 00:00:27,780 And here we get a list of all the metals that we can use to find a widget. 7 00:00:27,780 --> 00:00:33,160 And the one that we want is find by type like this. 8 00:00:33,180 --> 00:00:41,000 And so here we can pass braised bottom as an argument and then we need to write an expectation. 9 00:00:41,010 --> 00:00:49,640 So here I can type expect that button and then I'm going to use something that is called a matter. 10 00:00:49,650 --> 00:00:58,590 And in this case I can type finds one widget like this and finds one way that is a specific matter that 11 00:00:58,590 --> 00:01:01,170 is defined in the flatter test package. 12 00:01:01,200 --> 00:01:07,920 So in a nutshell this code tries to find a widget of type raised button inside the widget 3 that is 13 00:01:07,920 --> 00:01:11,080 returned by the custom raised but the widget. 14 00:01:11,370 --> 00:01:16,630 And then we expect that we find exactly one match by using this matter constant. 15 00:01:17,070 --> 00:01:21,690 So let's run the tests again OK. 16 00:01:21,730 --> 00:01:26,650 So let's get some more practice using matters by writing another expectation. 17 00:01:26,650 --> 00:01:31,930 And here I could dive extract and then find that y type. 18 00:01:32,200 --> 00:01:42,130 And this time I is flat bottom and then I want my matter to be fines nothing like this and finds nothing 19 00:01:42,130 --> 00:01:46,790 is a very common matter that is used to check that no we just are fun. 20 00:01:46,840 --> 00:01:53,620 So I could run the tests again and what we are saying here is that we expect to find our raised button 21 00:01:53,860 --> 00:01:55,690 but not a flat bottom. 22 00:01:55,780 --> 00:01:57,770 And our tests have passed again. 23 00:01:58,290 --> 00:01:58,570 OK. 24 00:01:58,600 --> 00:02:01,240 So let's take things one step further. 25 00:02:01,240 --> 00:02:05,650 And as you can see this custom raised button takes an optional child. 26 00:02:05,650 --> 00:02:09,840 We did and this is normally used to add some text inside a button. 27 00:02:10,240 --> 00:02:13,030 So as our next step we cannot a child. 28 00:02:13,030 --> 00:02:18,370 We did when we create this button and here we can pass up the text. 29 00:02:18,550 --> 00:02:21,780 We did that says stop me for example. 30 00:02:21,960 --> 00:02:29,920 And if we want here we can right expect and then find and this time we can say text and we're going 31 00:02:29,920 --> 00:02:31,060 to use the same string. 32 00:02:31,060 --> 00:02:37,150 So to me like this and we are going to use finds one widget as a matter. 33 00:02:37,600 --> 00:02:39,880 So let's run this test again. 34 00:02:40,000 --> 00:02:46,030 And the idea here is that we can pass a custom child to our widget and because this is a text widget 35 00:02:46,270 --> 00:02:50,220 then we can find that we did with the text that was used to configure it. 36 00:02:50,560 --> 00:02:53,260 And once again our test is green. 37 00:02:53,260 --> 00:02:59,260 In summary we have discovered how we can check if a widget contains another widget either white type 38 00:02:59,440 --> 00:03:01,150 or with a specific text. 39 00:03:01,150 --> 00:03:04,380 And to do that we need to use finders and matters. 40 00:03:04,420 --> 00:03:06,510 So let's continue on the next video. 4016

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.