Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
In this video I'm going to give an overview about testing in flutter and I will place to start with
this.
Is this page on the flatter documentation.
And if we read this we can find out that flatter supports three types of tests and these are a unit.
We did an integration tests and while this section covers testing in detail I also encourage you to
try some of the recipes on this page as they cover the basics quite well.
OK.
So it's now time to look at the distinction between unit.
We did an integration tests and according to the documentation our unit test tests are single function
method of class.
And the goal of our unit test is to verify the correctness of our unit of logic.
And there are a variety of conditions.
And in general.
Unit tests are the simplest kind of test that we can encounter.
And they also run very fast.
So it is common for projects to have a lot of unit tests because they can test specific things at a
very granular level.
But we need a lot of them to get good test coverage.
Then we have widget tests and these are used to test a single widget.
And the goal of what we did test is to verify that we just UI eye looks and interacts as expected and
as we will see they require a little bit more setup than unit tests but they can give us more confidence
that our code works.
And finally we have the integration tests and the goal of an integration test is to check that the entire
up or a large part of the app works as expected and as we can read here.
The goal of an integration test is to verify that all the widgets and services being tested worked together
as expected.
Furthermore you can use integration tests to verify your app's performance.
So if we wanted we could view these three types of tests as layer of what is known as the test pyramid
and a good testing strategy.
Would they include all three of these layers.
Because this gives us the most confidence that our code works as intended and in any case the entire
picture about testing would not be complete without mentioning Continuous Integration Services.
So I will not be covering spy services in this course but in my experience I have used both code magic
and be tried in some of my client work and I found that they are both mature services that I would recommend
for flatter projects.
OK.
So let's continue on the next video.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.