1
00:00:06,130 --> 00:00:09,380
Hey everybody How's it going this is Caleb with Debb slopes dot com.

2
00:00:09,380 --> 00:00:12,380
And welcome to the section all about UI testing.

3
00:00:12,440 --> 00:00:19,140
I'm so stoked you're here and we're going to be talking in this video about what is UI testing.

4
00:00:19,400 --> 00:00:25,700
Well you probably guessed it is testing the user interface of your application and making sure that

5
00:00:25,700 --> 00:00:31,520
all of the interactions you've designed work as they were designed without the need for a developer

6
00:00:31,790 --> 00:00:37,340
to manually go in run the application tap all the buttons slide all the sliders and swipe left all the

7
00:00:37,340 --> 00:00:38,490
creepers.

8
00:00:38,570 --> 00:00:41,130
It lets you test this automatically.

9
00:00:41,150 --> 00:00:44,580
Sometimes this is referred to as UI automation testing.

10
00:00:44,840 --> 00:00:50,580
But for the most part all major platforms you know iOS Android web development.

11
00:00:50,780 --> 00:00:57,980
There is some kind of UI testing framework either built into the language or the SDK or it's from a

12
00:00:57,980 --> 00:01:03,980
third party and essentially it allows you to create a testing instance of your application and set up

13
00:01:03,980 --> 00:01:09,530
various scenarios tests where you can test a certain sequence of events.

14
00:01:09,590 --> 00:01:13,570
For every interactive All element that you can imagine.

15
00:01:13,580 --> 00:01:19,150
So for example I could set up a UI test that ensures that my onboarding experience pops up.

16
00:01:19,370 --> 00:01:21,580
Then a user swipes left three times.

17
00:01:21,620 --> 00:01:23,300
I guess you left this way.

18
00:01:23,300 --> 00:01:25,340
So the onboarding experience pops up.

19
00:01:25,340 --> 00:01:30,120
They swipe left three times to advance to the final page of the onboarding screen.

20
00:01:30,320 --> 00:01:33,280
Then they tap the done button to dismiss that controller.

21
00:01:33,380 --> 00:01:39,350
And then finally at the end I can verify that that screen did dismiss that it was deallocated and that

22
00:01:39,350 --> 00:01:41,480
it's no longer showing up on the screen.

23
00:01:41,930 --> 00:01:47,250
As you can imagine this is extremely efficient and helpful and it saves a ton of time for developers.

24
00:01:47,380 --> 00:01:50,750
That should be using their time to write code and not push buttons.

25
00:01:50,750 --> 00:01:55,920
So that is what UI testing is we can basically create a test instance of our application.

26
00:01:56,090 --> 00:02:01,250
We can run tests that set up certain scenarios to tap certain buttons and cause certain actions to happen

27
00:02:01,580 --> 00:02:05,490
on the screen for various devices and elements on our device.

28
00:02:05,540 --> 00:02:11,360
And now that we know what UI testing is let's dive into some best practices to consider when testing

29
00:02:11,590 --> 00:02:12,140
Acia there.